Warning: Permanently added '52.207.223.200' (ED25519) to the list of known hosts.
You can reproduce this build on your computer by running:
sudo dnf install copr-rpmbuild
/usr/bin/copr-rpmbuild --verbose --drop-resultdir --task-url https://copr.fedorainfracloud.org/backend/get-build-task/6278328-fedora-rawhide-x86_64 --chroot fedora-rawhide-x86_64
Version: 0.68
PID: 12543
Logging PID: 12544
Task:
{'appstream': False,
'background': False,
'build_id': 6278328,
'buildroot_pkgs': [],
'chroot': 'fedora-rawhide-x86_64',
'enable_net': False,
'fedora_review': False,
'git_hash': '6673635b9cf91c4b55485f3a3eeec4361e433d9f',
'git_repo': 'https://copr-dist-git.fedorainfracloud.org/git/thrnciar/python-wheel-92af55f9/python-django',
'isolation': 'default',
'memory_reqs': 2048,
'package_name': 'python-django',
'package_version': '4.2.3-1',
'project_dirname': 'python-wheel-92af55f9',
'project_name': 'python-wheel-92af55f9',
'project_owner': 'thrnciar',
'repos': [{'baseurl': 'https://download.copr.fedorainfracloud.org/results/thrnciar/python-wheel-92af55f9/fedora-rawhide-x86_64/',
'id': 'copr_base',
'name': 'Copr repository'}],
'sandbox': 'thrnciar/python-wheel-92af55f9--thrnciar',
'source_json': {},
'source_type': None,
'submitter': 'thrnciar',
'tags': [],
'task_id': '6278328-fedora-rawhide-x86_64',
'timeout': 18000,
'uses_devel_repo': False,
'with_opts': [],
'without_opts': []}
Running: git clone https://copr-dist-git.fedorainfracloud.org/git/thrnciar/python-wheel-92af55f9/python-django /var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django --depth 500 --no-single-branch --recursive
cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/thrnciar/python-wheel-92af55f9/python-django', '/var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django', '--depth', '500', '--no-single-branch', '--recursive']
cwd: .
rc: 0
stdout:
stderr: Cloning into '/var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django'...
Running: git checkout 6673635b9cf91c4b55485f3a3eeec4361e433d9f --
cmd: ['git', 'checkout', '6673635b9cf91c4b55485f3a3eeec4361e433d9f', '--']
cwd: /var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django
rc: 0
stdout:
stderr: Note: switching to '6673635b9cf91c4b55485f3a3eeec4361e433d9f'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 6673635 automatic import of python-django
Running: copr-distgit-client sources
/usr/bin/tail: /var/lib/copr-rpmbuild/main.log: file truncated
cmd: ['copr-distgit-client', 'sources']
cwd: /var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django
rc: 0
stdout:
stderr: INFO: Reading stdout from command: git rev-parse --abbrev-ref HEAD
INFO: Reading stdout from command: git rev-parse HEAD
INFO: Reading sources specification file: sources
INFO: Downloading Django-4.2.3.tar.gz
INFO: Calling: curl -H Pragma: -o Django-4.2.3.tar.gz --location --remote-time --show-error --fail https://copr-dist-git.fedorainfracloud.org/repo/pkgs/thrnciar/python-wheel-92af55f9/python-django/Django-4.2.3.tar.gz/md5/eaa70abe96b6e6b50ef297531c365265/Django-4.2.3.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 9.9M 100 9.9M 0 0 115M 0 --:--:-- --:--:-- --:--:-- 116M
INFO: Reading stdout from command: md5sum Django-4.2.3.tar.gz
Running (timeout=18000): unbuffer mock --buildsrpm --spec /var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django/python-django.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1692096785.491105 -r /var/lib/copr-rpmbuild/results/configs/child.cfg
INFO: mock.py version 5.0 starting (python version = 3.11.3, NVR = mock-5.0-1.fc38)...
Start(bootstrap): init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish(bootstrap): init plugins
Start: init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish: init plugins
INFO: Signal handler active
Start: run
INFO: Start(/var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django/python-django.spec) Config(fedora-rawhide-x86_64)
Start: clean chroot
Finish: clean chroot
Mock Version: 5.0
INFO: Mock Version: 5.0
Start(bootstrap): chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1692096785.491105/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Using bootstrap image: registry.fedoraproject.org/fedora:rawhide
INFO: Pulling image: registry.fedoraproject.org/fedora:rawhide
INFO: Copy content of container registry.fedoraproject.org/fedora:rawhide to /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1692096785.491105/root
INFO: mounting registry.fedoraproject.org/fedora:rawhide with podman image mount
INFO: image registry.fedoraproject.org/fedora:rawhide as /var/lib/containers/storage/overlay/a2c9f22408b74714d9cd5219089c17bd0236fe70d5fd6c04f5a7037cac14cbf1/merged
INFO: umounting image registry.fedoraproject.org/fedora:rawhide (/var/lib/containers/storage/overlay/a2c9f22408b74714d9cd5219089c17bd0236fe70d5fd6c04f5a7037cac14cbf1/merged) with podman image umount
INFO: Package manager dnf detected and used (fallback)
INFO: Bootstrap image not marked ready
Start(bootstrap): installing dnf tooling
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 42 MB/s | 1.7 MB 00:00
fedora 48 MB/s | 73 MB 00:01
Package python3-dnf-4.16.2-2.fc39.noarch is already installed.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
python3-dnf-plugins-core noarch 4.4.2-1.fc39 fedora 293 k
Installing dependencies:
dbus-libs x86_64 1:1.14.8-2.fc39 fedora 156 k
python3-dateutil noarch 1:2.8.2-10.fc39 fedora 355 k
python3-dbus x86_64 1.3.2-4.fc40 copr_base 147 k
python3-distro noarch 1.8.0-6.fc39 fedora 49 k
python3-six noarch 1.16.0-12.fc39 fedora 41 k
python3-systemd x86_64 235-5.fc39 fedora 107 k
Transaction Summary
================================================================================
Install 7 Packages
Total download size: 1.1 M
Installed size: 3.5 M
Downloading Packages:
(1/7): dbus-libs-1.14.8-2.fc39.x86_64.rpm 9.3 MB/s | 156 kB 00:00
(2/7): python3-distro-1.8.0-6.fc39.noarch.rpm 37 MB/s | 49 kB 00:00
(3/7): python3-dbus-1.3.2-4.fc40.x86_64.rpm 7.5 MB/s | 147 kB 00:00
(4/7): python3-dnf-plugins-core-4.4.2-1.fc39.no 110 MB/s | 293 kB 00:00
(5/7): python3-dateutil-2.8.2-10.fc39.noarch.rp 16 MB/s | 355 kB 00:00
(6/7): python3-six-1.16.0-12.fc39.noarch.rpm 12 MB/s | 41 kB 00:00
(7/7): python3-systemd-235-5.fc39.x86_64.rpm 65 MB/s | 107 kB 00:00
--------------------------------------------------------------------------------
Total 12 MB/s | 1.1 MB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : python3-systemd-235-5.fc39.x86_64 1/7
Installing : python3-six-1.16.0-12.fc39.noarch 2/7
Installing : python3-dateutil-1:2.8.2-10.fc39.noarch 3/7
Installing : python3-distro-1.8.0-6.fc39.noarch 4/7
Installing : dbus-libs-1:1.14.8-2.fc39.x86_64 5/7
Installing : python3-dbus-1.3.2-4.fc40.x86_64 6/7
Installing : python3-dnf-plugins-core-4.4.2-1.fc39.noarch 7/7
Running scriptlet: python3-dnf-plugins-core-4.4.2-1.fc39.noarch 7/7
Verifying : python3-dbus-1.3.2-4.fc40.x86_64 1/7
Verifying : dbus-libs-1:1.14.8-2.fc39.x86_64 2/7
Verifying : python3-dateutil-1:2.8.2-10.fc39.noarch 3/7
Verifying : python3-distro-1.8.0-6.fc39.noarch 4/7
Verifying : python3-dnf-plugins-core-4.4.2-1.fc39.noarch 5/7
Verifying : python3-six-1.16.0-12.fc39.noarch 6/7
Verifying : python3-systemd-235-5.fc39.x86_64 7/7
Installed:
dbus-libs-1:1.14.8-2.fc39.x86_64
python3-dateutil-1:2.8.2-10.fc39.noarch
python3-dbus-1.3.2-4.fc40.x86_64
python3-distro-1.8.0-6.fc39.noarch
python3-dnf-plugins-core-4.4.2-1.fc39.noarch
python3-six-1.16.0-12.fc39.noarch
python3-systemd-235-5.fc39.x86_64
Complete!
Finish(bootstrap): installing dnf tooling
Start(bootstrap): creating root cache
Finish(bootstrap): creating root cache
Finish(bootstrap): chroot init
Start: chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Package manager dnf detected and used (direct choice)
Start: installing minimal buildroot with dnf
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 81 kB/s | 1.5 kB 00:00
Copr repository 45 MB/s | 1.7 MB 00:00
fedora 262 kB/s | 22 kB 00:00
Dependencies resolved.
================================================================================
Package Arch Version Repo Size
================================================================================
Installing group/module packages:
bash x86_64 5.2.15-5.fc39 fedora 1.8 M
bzip2 x86_64 1.0.8-16.fc39 fedora 52 k
coreutils x86_64 9.3-2.fc39 fedora 1.1 M
cpio x86_64 2.14-4.fc39 fedora 279 k
diffutils x86_64 3.10-3.fc39 fedora 398 k
fedora-release-common noarch 40-0.2 fedora 17 k
findutils x86_64 1:4.9.0-5.fc39 fedora 492 k
gawk x86_64 5.2.2-2.fc39 fedora 1.1 M
glibc-minimal-langpack x86_64 2.38-1.fc39 fedora 67 k
grep x86_64 3.11-5.fc40 fedora 298 k
gzip x86_64 1.12-6.fc39 fedora 166 k
info x86_64 7.0.3-3.fc39 fedora 182 k
patch x86_64 2.7.6-22.fc39 fedora 125 k
redhat-rpm-config noarch 262-1.fc39 fedora 84 k
rpm-build x86_64 4.18.92-1.fc39 fedora 78 k
sed x86_64 4.8-14.fc39 fedora 306 k
shadow-utils x86_64 2:4.13-8.fc39 fedora 1.3 M
tar x86_64 2:1.35-1.fc39 fedora 862 k
unzip x86_64 6.0-62.fc39 fedora 184 k
util-linux x86_64 2.39.1-3.fc39 fedora 1.2 M
which x86_64 2.21-40.fc39 fedora 42 k
xz x86_64 5.4.4-1.fc39 fedora 556 k
Installing dependencies:
alternatives x86_64 1.25-1.fc39 fedora 39 k
ansible-srpm-macros noarch 1-11.fc39 fedora 21 k
audit-libs x86_64 3.1.2-1.fc39 fedora 117 k
authselect x86_64 1.4.2-3.fc39 fedora 144 k
authselect-libs x86_64 1.4.2-3.fc39 fedora 249 k
basesystem noarch 11-18.fc39 fedora 7.2 k
binutils x86_64 2.40-13.fc39 fedora 5.6 M
binutils-gold x86_64 2.40-13.fc39 fedora 797 k
bzip2-libs x86_64 1.0.8-16.fc39 fedora 41 k
ca-certificates noarch 2023.2.60_v7.0.306-2.fc39 fedora 837 k
coreutils-common x86_64 9.3-2.fc39 fedora 2.1 M
cracklib x86_64 2.9.11-2.fc39 fedora 94 k
crypto-policies noarch 20230731-1.git5ed06e0.fc39 fedora 99 k
curl x86_64 8.2.1-2.fc40 fedora 346 k
cyrus-sasl-lib x86_64 2.1.28-11.fc39 fedora 793 k
debugedit x86_64 5.0-10.fc39 fedora 77 k
dwz x86_64 0.15-3.fc39 fedora 134 k
ed x86_64 1.19-4.fc39 fedora 79 k
efi-srpm-macros noarch 5-9.fc39 fedora 22 k
elfutils x86_64 0.189-4.fc39 fedora 537 k
elfutils-debuginfod-client x86_64 0.189-4.fc39 fedora 38 k
elfutils-default-yama-scope noarch 0.189-4.fc39 fedora 13 k
elfutils-libelf x86_64 0.189-4.fc39 fedora 194 k
elfutils-libs x86_64 0.189-4.fc39 fedora 258 k
fedora-gpg-keys noarch 40-0.1 fedora 130 k
fedora-release noarch 40-0.2 fedora 7.2 k
fedora-release-identity-basic
noarch 40-0.2 fedora 8.0 k
fedora-repos noarch 40-0.1 fedora 9.4 k
fedora-repos-rawhide noarch 40-0.1 fedora 9.0 k
file x86_64 5.44-5.fc39 fedora 49 k
file-libs x86_64 5.44-5.fc39 fedora 729 k
filesystem x86_64 3.18-6.fc39 fedora 1.1 M
fonts-srpm-macros noarch 1:2.0.5-12.fc39 fedora 26 k
fpc-srpm-macros noarch 1.3-8.fc39 fedora 7.4 k
gdb-minimal x86_64 13.2-7.fc39 fedora 4.2 M
gdbm-libs x86_64 1:1.23-4.fc39 fedora 56 k
ghc-srpm-macros noarch 1.6.1-2.fc39 fedora 7.8 k
glibc x86_64 2.38-1.fc39 fedora 2.2 M
glibc-common x86_64 2.38-1.fc39 fedora 348 k
glibc-gconv-extra x86_64 2.38-1.fc39 fedora 1.6 M
gmp x86_64 1:6.2.1-5.fc39 fedora 313 k
gnat-srpm-macros noarch 6-3.fc39 fedora 8.8 k
go-srpm-macros noarch 3.2.0-6.fc39 fedora 27 k
jansson x86_64 2.13.1-7.fc39 fedora 44 k
kernel-srpm-macros noarch 1.0-20.fc39 fedora 10 k
keyutils-libs x86_64 1.6.1-7.fc39 fedora 31 k
krb5-libs x86_64 1.21-3.fc39 fedora 765 k
libacl x86_64 2.3.1-8.fc39 fedora 23 k
libarchive x86_64 3.7.1-1.fc39 fedora 408 k
libattr x86_64 2.5.1-8.fc39 fedora 18 k
libblkid x86_64 2.39.1-3.fc39 fedora 116 k
libbrotli x86_64 1.0.9-13.fc39 fedora 317 k
libcap x86_64 2.48-7.fc39 fedora 68 k
libcap-ng x86_64 0.8.3-7.fc39 fedora 32 k
libcom_err x86_64 1.47.0-2.fc39 fedora 26 k
libcurl x86_64 8.2.1-2.fc40 fedora 328 k
libdb x86_64 5.3.28-56.fc39 fedora 760 k
libeconf x86_64 0.4.0-6.fc39 fedora 27 k
libevent x86_64 2.1.12-9.fc39 fedora 258 k
libfdisk x86_64 2.39.1-3.fc39 fedora 162 k
libffi x86_64 3.4.4-4.fc39 fedora 40 k
libgcc x86_64 13.2.1-1.fc39 fedora 109 k
libgomp x86_64 13.2.1-1.fc39 fedora 319 k
libidn2 x86_64 2.3.4-3.fc39 fedora 117 k
libmount x86_64 2.39.1-3.fc39 fedora 154 k
libnghttp2 x86_64 1.55.1-2.fc39 fedora 75 k
libnsl2 x86_64 2.0.0-6.fc39 fedora 30 k
libpkgconf x86_64 1.9.5-2.fc39 fedora 38 k
libpsl x86_64 0.21.2-4.fc39 fedora 63 k
libpwquality x86_64 1.4.5-6.fc39 fedora 120 k
libselinux x86_64 3.5-5.fc40 copr_base 87 k
libsemanage x86_64 3.5-4.fc39 fedora 120 k
libsepol x86_64 3.5-2.fc39 fedora 324 k
libsigsegv x86_64 2.14-5.fc39 fedora 27 k
libsmartcols x86_64 2.39.1-3.fc39 fedora 67 k
libssh x86_64 0.10.5-2.fc39 fedora 211 k
libssh-config noarch 0.10.5-2.fc39 fedora 9.2 k
libstdc++ x86_64 13.2.1-1.fc39 fedora 860 k
libtasn1 x86_64 4.19.0-3.fc39 fedora 74 k
libtirpc x86_64 1.3.3-1.rc2.fc39 fedora 94 k
libunistring x86_64 1.1-4.fc39 fedora 543 k
libutempter x86_64 1.2.1-10.fc39 fedora 26 k
libuuid x86_64 2.39.1-3.fc39 fedora 28 k
libverto x86_64 0.3.2-6.fc39 fedora 20 k
libxcrypt x86_64 4.4.36-2.fc39 fedora 119 k
libxml2 x86_64 2.10.4-3.fc39 fedora 701 k
libzstd x86_64 1.5.5-4.fc39 fedora 309 k
lua-libs x86_64 5.4.6-3.fc39 fedora 133 k
lua-srpm-macros noarch 1-9.fc39 fedora 8.6 k
lz4-libs x86_64 1.9.4-4.fc39 fedora 67 k
mpfr x86_64 4.2.0-3.fc39 fedora 344 k
ncurses-base noarch 6.4-6.20230520.fc39 fedora 88 k
ncurses-libs x86_64 6.4-6.20230520.fc39 fedora 336 k
ocaml-srpm-macros noarch 8-2.fc39 fedora 14 k
openblas-srpm-macros noarch 2-14.fc39 fedora 7.5 k
openldap x86_64 2.6.6-1.fc39 fedora 255 k
openssl-libs x86_64 1:3.1.1-1.fc39 fedora 2.2 M
p11-kit x86_64 0.25.0-2.fc39 fedora 486 k
p11-kit-trust x86_64 0.25.0-2.fc39 fedora 142 k
package-notes-srpm-macros noarch 0.5-9.fc39 fedora 11 k
pam x86_64 1.5.3-2.fc39 fedora 548 k
pam-libs x86_64 1.5.3-2.fc39 fedora 58 k
pcre2 x86_64 10.42-1.fc39.2 fedora 233 k
pcre2-syntax noarch 10.42-1.fc39.2 fedora 143 k
perl-srpm-macros noarch 1-51.fc39 fedora 8.0 k
pkgconf x86_64 1.9.5-2.fc39 fedora 42 k
pkgconf-m4 noarch 1.9.5-2.fc39 fedora 14 k
pkgconf-pkg-config x86_64 1.9.5-2.fc39 fedora 9.6 k
popt x86_64 1.19-3.fc39 fedora 66 k
publicsuffix-list-dafsa noarch 20230614-2.fc39 fedora 57 k
pyproject-srpm-macros noarch 1.9.0-2.fc40 copr_base 15 k
python-srpm-macros noarch 3.12-2.fc39 fedora 25 k
qt5-srpm-macros noarch 5.15.10-2.fc39 fedora 8.3 k
qt6-srpm-macros noarch 6.5.2-2.fc39 fedora 9.2 k
readline x86_64 8.2-4.fc39 fedora 213 k
rpm x86_64 4.18.92-1.fc39 fedora 533 k
rpm-build-libs x86_64 4.18.92-1.fc39 fedora 96 k
rpm-libs x86_64 4.18.92-1.fc39 fedora 312 k
rpm-sequoia x86_64 1.4.1-2.fc39 fedora 869 k
rpmautospec-rpm-macros noarch 0.3.5-4.fc39 fedora 8.8 k
rust-srpm-macros noarch 24-3.fc39 fedora 12 k
setup noarch 2.14.4-1.fc39 fedora 154 k
sqlite-libs x86_64 3.42.0-7.fc39 fedora 678 k
systemd-libs x86_64 254.1-2.fc40 fedora 688 k
tzdata noarch 2023c-2.fc39 fedora 718 k
util-linux-core x86_64 2.39.1-3.fc39 fedora 494 k
xxhash-libs x86_64 0.8.2-1.fc39 fedora 37 k
xz-libs x86_64 5.4.4-1.fc39 fedora 108 k
zip x86_64 3.0-38.fc39 fedora 266 k
zlib x86_64 1.2.13-4.fc39 fedora 94 k
zstd x86_64 1.5.5-4.fc39 fedora 482 k
Installing Groups:
Buildsystem building group
Transaction Summary
================================================================================
Install 153 Packages
Total size: 53 M
Installed size: 180 M
Downloading Packages:
[SKIPPED] libselinux-3.5-5.fc40.x86_64.rpm: Already downloaded
[SKIPPED] pyproject-srpm-macros-1.9.0-2.fc40.noarch.rpm: Already downloaded
[SKIPPED] alternatives-1.25-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] ansible-srpm-macros-1-11.fc39.noarch.rpm: Already downloaded
[SKIPPED] audit-libs-3.1.2-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] authselect-1.4.2-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] authselect-libs-1.4.2-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] basesystem-11-18.fc39.noarch.rpm: Already downloaded
[SKIPPED] bash-5.2.15-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] binutils-2.40-13.fc39.x86_64.rpm: Already downloaded
[SKIPPED] binutils-gold-2.40-13.fc39.x86_64.rpm: Already downloaded
[SKIPPED] bzip2-1.0.8-16.fc39.x86_64.rpm: Already downloaded
[SKIPPED] bzip2-libs-1.0.8-16.fc39.x86_64.rpm: Already downloaded
[SKIPPED] ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] coreutils-9.3-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] coreutils-common-9.3-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] cpio-2.14-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] cracklib-2.9.11-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] crypto-policies-20230731-1.git5ed06e0.fc39.noarch.rpm: Already downloaded
[SKIPPED] curl-8.2.1-2.fc40.x86_64.rpm: Already downloaded
[SKIPPED] cyrus-sasl-lib-2.1.28-11.fc39.x86_64.rpm: Already downloaded
[SKIPPED] debugedit-5.0-10.fc39.x86_64.rpm: Already downloaded
[SKIPPED] diffutils-3.10-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] dwz-0.15-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] ed-1.19-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] efi-srpm-macros-5-9.fc39.noarch.rpm: Already downloaded
[SKIPPED] elfutils-0.189-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] elfutils-debuginfod-client-0.189-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] elfutils-default-yama-scope-0.189-4.fc39.noarch.rpm: Already downloaded
[SKIPPED] elfutils-libelf-0.189-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] elfutils-libs-0.189-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] fedora-gpg-keys-40-0.1.noarch.rpm: Already downloaded
[SKIPPED] fedora-release-40-0.2.noarch.rpm: Already downloaded
[SKIPPED] fedora-release-common-40-0.2.noarch.rpm: Already downloaded
[SKIPPED] fedora-release-identity-basic-40-0.2.noarch.rpm: Already downloaded
[SKIPPED] fedora-repos-40-0.1.noarch.rpm: Already downloaded
[SKIPPED] fedora-repos-rawhide-40-0.1.noarch.rpm: Already downloaded
[SKIPPED] file-5.44-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] file-libs-5.44-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] filesystem-3.18-6.fc39.x86_64.rpm: Already downloaded
[SKIPPED] findutils-4.9.0-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] fonts-srpm-macros-2.0.5-12.fc39.noarch.rpm: Already downloaded
[SKIPPED] fpc-srpm-macros-1.3-8.fc39.noarch.rpm: Already downloaded
[SKIPPED] gawk-5.2.2-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] gdb-minimal-13.2-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] gdbm-libs-1.23-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] ghc-srpm-macros-1.6.1-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] glibc-2.38-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] glibc-common-2.38-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] glibc-gconv-extra-2.38-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] glibc-minimal-langpack-2.38-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] gmp-6.2.1-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] gnat-srpm-macros-6-3.fc39.noarch.rpm: Already downloaded
[SKIPPED] go-srpm-macros-3.2.0-6.fc39.noarch.rpm: Already downloaded
[SKIPPED] grep-3.11-5.fc40.x86_64.rpm: Already downloaded
[SKIPPED] gzip-1.12-6.fc39.x86_64.rpm: Already downloaded
[SKIPPED] info-7.0.3-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] jansson-2.13.1-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] kernel-srpm-macros-1.0-20.fc39.noarch.rpm: Already downloaded
[SKIPPED] keyutils-libs-1.6.1-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] krb5-libs-1.21-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libacl-2.3.1-8.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libarchive-3.7.1-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libattr-2.5.1-8.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libblkid-2.39.1-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libbrotli-1.0.9-13.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libcap-2.48-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libcap-ng-0.8.3-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libcom_err-1.47.0-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libcurl-8.2.1-2.fc40.x86_64.rpm: Already downloaded
[SKIPPED] libdb-5.3.28-56.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libeconf-0.4.0-6.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libevent-2.1.12-9.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libfdisk-2.39.1-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libffi-3.4.4-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libgcc-13.2.1-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libgomp-13.2.1-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libidn2-2.3.4-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libmount-2.39.1-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libnghttp2-1.55.1-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libnsl2-2.0.0-6.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libpkgconf-1.9.5-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libpsl-0.21.2-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libpwquality-1.4.5-6.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libsemanage-3.5-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libsepol-3.5-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libsigsegv-2.14-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libsmartcols-2.39.1-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libssh-0.10.5-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libssh-config-0.10.5-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] libstdc++-13.2.1-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libtasn1-4.19.0-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libtirpc-1.3.3-1.rc2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libunistring-1.1-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libutempter-1.2.1-10.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libuuid-2.39.1-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libverto-0.3.2-6.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libxcrypt-4.4.36-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libxml2-2.10.4-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libzstd-1.5.5-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] lua-libs-5.4.6-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] lua-srpm-macros-1-9.fc39.noarch.rpm: Already downloaded
[SKIPPED] lz4-libs-1.9.4-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] mpfr-4.2.0-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] ncurses-base-6.4-6.20230520.fc39.noarch.rpm: Already downloaded
[SKIPPED] ncurses-libs-6.4-6.20230520.fc39.x86_64.rpm: Already downloaded
[SKIPPED] ocaml-srpm-macros-8-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] openblas-srpm-macros-2-14.fc39.noarch.rpm: Already downloaded
[SKIPPED] openldap-2.6.6-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] openssl-libs-3.1.1-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] p11-kit-0.25.0-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] p11-kit-trust-0.25.0-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] package-notes-srpm-macros-0.5-9.fc39.noarch.rpm: Already downloaded
[SKIPPED] pam-1.5.3-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] pam-libs-1.5.3-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] patch-2.7.6-22.fc39.x86_64.rpm: Already downloaded
[SKIPPED] pcre2-10.42-1.fc39.2.x86_64.rpm: Already downloaded
[SKIPPED] pcre2-syntax-10.42-1.fc39.2.noarch.rpm: Already downloaded
[SKIPPED] perl-srpm-macros-1-51.fc39.noarch.rpm: Already downloaded
[SKIPPED] pkgconf-1.9.5-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] pkgconf-m4-1.9.5-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] pkgconf-pkg-config-1.9.5-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] popt-1.19-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] publicsuffix-list-dafsa-20230614-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] python-srpm-macros-3.12-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] qt5-srpm-macros-5.15.10-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] qt6-srpm-macros-6.5.2-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] readline-8.2-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] redhat-rpm-config-262-1.fc39.noarch.rpm: Already downloaded
[SKIPPED] rpm-4.18.92-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] rpm-build-4.18.92-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] rpm-build-libs-4.18.92-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] rpm-libs-4.18.92-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] rpm-sequoia-1.4.1-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] rpmautospec-rpm-macros-0.3.5-4.fc39.noarch.rpm: Already downloaded
[SKIPPED] rust-srpm-macros-24-3.fc39.noarch.rpm: Already downloaded
[SKIPPED] sed-4.8-14.fc39.x86_64.rpm: Already downloaded
[SKIPPED] setup-2.14.4-1.fc39.noarch.rpm: Already downloaded
[SKIPPED] shadow-utils-4.13-8.fc39.x86_64.rpm: Already downloaded
[SKIPPED] sqlite-libs-3.42.0-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] systemd-libs-254.1-2.fc40.x86_64.rpm: Already downloaded
[SKIPPED] tar-1.35-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] tzdata-2023c-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] unzip-6.0-62.fc39.x86_64.rpm: Already downloaded
[SKIPPED] util-linux-2.39.1-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] util-linux-core-2.39.1-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] which-2.21-40.fc39.x86_64.rpm: Already downloaded
[SKIPPED] xxhash-libs-0.8.2-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] xz-5.4.4-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] xz-libs-5.4.4-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] zip-3.0-38.fc39.x86_64.rpm: Already downloaded
[SKIPPED] zlib-1.2.13-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] zstd-1.5.5-4.fc39.x86_64.rpm: Already downloaded
fedora 1.6 MB/s | 1.6 kB 00:00
Importing GPG key 0xA15B79CC:
Userid : "Fedora (40) <fedora-40-primary@fedoraproject.org>"
Fingerprint: 115D F9AE F857 853E E844 5D0A 0727 707E A15B 79CC
From : /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-40-primary
Key imported successfully
fedora 1.6 MB/s | 1.6 kB 00:00
GPG key at file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-40-primary (0xA15B79CC) is already installed
fedora 1.6 MB/s | 1.6 kB 00:00
Importing GPG key 0x18B8E74C:
Userid : "Fedora (39) <fedora-39-primary@fedoraproject.org>"
Fingerprint: E8F2 3996 F232 1864 0CB4 4CBE 75CF 5AC4 18B8 E74C
From : /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-39-primary
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Running scriptlet: filesystem-3.18-6.fc39.x86_64 1/1
Preparing : 1/1
Installing : libgcc-13.2.1-1.fc39.x86_64 1/153
Running scriptlet: libgcc-13.2.1-1.fc39.x86_64 1/153
Installing : crypto-policies-20230731-1.git5ed06e0.fc39.noarc 2/153
Running scriptlet: crypto-policies-20230731-1.git5ed06e0.fc39.noarc 2/153
Installing : tzdata-2023c-2.fc39.noarch 3/153
Installing : fedora-release-identity-basic-40-0.2.noarch 4/153
Installing : fedora-repos-rawhide-40-0.1.noarch 5/153
Installing : fedora-gpg-keys-40-0.1.noarch 6/153
Installing : fedora-repos-40-0.1.noarch 7/153
Installing : fedora-release-common-40-0.2.noarch 8/153
Installing : fedora-release-40-0.2.noarch 9/153
Installing : setup-2.14.4-1.fc39.noarch 10/153
warning: /etc/hosts created as /etc/hosts.rpmnew
Running scriptlet: setup-2.14.4-1.fc39.noarch 10/153
Installing : filesystem-3.18-6.fc39.x86_64 11/153
Installing : basesystem-11-18.fc39.noarch 12/153
Installing : rust-srpm-macros-24-3.fc39.noarch 13/153
Installing : qt6-srpm-macros-6.5.2-2.fc39.noarch 14/153
Installing : qt5-srpm-macros-5.15.10-2.fc39.noarch 15/153
Installing : publicsuffix-list-dafsa-20230614-2.fc39.noarch 16/153
Installing : pkgconf-m4-1.9.5-2.fc39.noarch 17/153
Installing : perl-srpm-macros-1-51.fc39.noarch 18/153
Installing : pcre2-syntax-10.42-1.fc39.2.noarch 19/153
Installing : package-notes-srpm-macros-0.5-9.fc39.noarch 20/153
Installing : openblas-srpm-macros-2-14.fc39.noarch 21/153
Installing : ocaml-srpm-macros-8-2.fc39.noarch 22/153
Installing : ncurses-base-6.4-6.20230520.fc39.noarch 23/153
Installing : glibc-gconv-extra-2.38-1.fc39.x86_64 24/153
Running scriptlet: glibc-gconv-extra-2.38-1.fc39.x86_64 24/153
Installing : glibc-minimal-langpack-2.38-1.fc39.x86_64 25/153
Installing : glibc-common-2.38-1.fc39.x86_64 26/153
Running scriptlet: glibc-2.38-1.fc39.x86_64 27/153
Installing : glibc-2.38-1.fc39.x86_64 27/153
Running scriptlet: glibc-2.38-1.fc39.x86_64 27/153
Installing : ncurses-libs-6.4-6.20230520.fc39.x86_64 28/153
Installing : bash-5.2.15-5.fc39.x86_64 29/153
Running scriptlet: bash-5.2.15-5.fc39.x86_64 29/153
Installing : zlib-1.2.13-4.fc39.x86_64 30/153
Installing : xz-libs-5.4.4-1.fc39.x86_64 31/153
Installing : bzip2-libs-1.0.8-16.fc39.x86_64 32/153
Installing : libstdc++-13.2.1-1.fc39.x86_64 33/153
Installing : libuuid-2.39.1-3.fc39.x86_64 34/153
Installing : libzstd-1.5.5-4.fc39.x86_64 35/153
Installing : elfutils-libelf-0.189-4.fc39.x86_64 36/153
Installing : popt-1.19-3.fc39.x86_64 37/153
Installing : libblkid-2.39.1-3.fc39.x86_64 38/153
Installing : readline-8.2-4.fc39.x86_64 39/153
Installing : gmp-1:6.2.1-5.fc39.x86_64 40/153
Installing : libattr-2.5.1-8.fc39.x86_64 41/153
Installing : libacl-2.3.1-8.fc39.x86_64 42/153
Installing : libcap-2.48-7.fc39.x86_64 43/153
Installing : libxcrypt-4.4.36-2.fc39.x86_64 44/153
Installing : lz4-libs-1.9.4-4.fc39.x86_64 45/153
Installing : systemd-libs-254.1-2.fc40.x86_64 46/153
Installing : mpfr-4.2.0-3.fc39.x86_64 47/153
Installing : dwz-0.15-3.fc39.x86_64 48/153
Installing : unzip-6.0-62.fc39.x86_64 49/153
Installing : file-libs-5.44-5.fc39.x86_64 50/153
Installing : file-5.44-5.fc39.x86_64 51/153
Installing : alternatives-1.25-1.fc39.x86_64 52/153
Installing : jansson-2.13.1-7.fc39.x86_64 53/153
Installing : libcap-ng-0.8.3-7.fc39.x86_64 54/153
Installing : audit-libs-3.1.2-1.fc39.x86_64 55/153
Installing : pam-libs-1.5.3-2.fc39.x86_64 56/153
Installing : libcom_err-1.47.0-2.fc39.x86_64 57/153
Installing : libsepol-3.5-2.fc39.x86_64 58/153
Installing : libsmartcols-2.39.1-3.fc39.x86_64 59/153
Installing : libunistring-1.1-4.fc39.x86_64 60/153
Installing : libidn2-2.3.4-3.fc39.x86_64 61/153
Installing : lua-libs-5.4.6-3.fc39.x86_64 62/153
Installing : pcre2-10.42-1.fc39.2.x86_64 63/153
Installing : libselinux-3.5-5.fc40.x86_64 64/153
Installing : sed-4.8-14.fc39.x86_64 65/153
Installing : grep-3.11-5.fc40.x86_64 66/153
Installing : findutils-1:4.9.0-5.fc39.x86_64 67/153
Installing : xz-5.4.4-1.fc39.x86_64 68/153
Installing : libmount-2.39.1-3.fc39.x86_64 69/153
Installing : util-linux-core-2.39.1-3.fc39.x86_64 70/153
Installing : libsemanage-3.5-4.fc39.x86_64 71/153
Installing : tar-2:1.35-1.fc39.x86_64 72/153
Installing : libpsl-0.21.2-4.fc39.x86_64 73/153
Installing : zip-3.0-38.fc39.x86_64 74/153
Installing : zstd-1.5.5-4.fc39.x86_64 75/153
Installing : libfdisk-2.39.1-3.fc39.x86_64 76/153
Installing : bzip2-1.0.8-16.fc39.x86_64 77/153
Installing : libxml2-2.10.4-3.fc39.x86_64 78/153
Installing : sqlite-libs-3.42.0-7.fc39.x86_64 79/153
Installing : ed-1.19-4.fc39.x86_64 80/153
Installing : patch-2.7.6-22.fc39.x86_64 81/153
Installing : elfutils-default-yama-scope-0.189-4.fc39.noarch 82/153
Running scriptlet: elfutils-default-yama-scope-0.189-4.fc39.noarch 82/153
Installing : cpio-2.14-4.fc39.x86_64 83/153
Installing : diffutils-3.10-3.fc39.x86_64 84/153
Installing : gdbm-libs-1:1.23-4.fc39.x86_64 85/153
Installing : cyrus-sasl-lib-2.1.28-11.fc39.x86_64 86/153
Installing : keyutils-libs-1.6.1-7.fc39.x86_64 87/153
Installing : libbrotli-1.0.9-13.fc39.x86_64 88/153
Installing : libdb-5.3.28-56.fc39.x86_64 89/153
Installing : libeconf-0.4.0-6.fc39.x86_64 90/153
Installing : shadow-utils-2:4.13-8.fc39.x86_64 91/153
Running scriptlet: libutempter-1.2.1-10.fc39.x86_64 92/153
Installing : libutempter-1.2.1-10.fc39.x86_64 92/153
Installing : libffi-3.4.4-4.fc39.x86_64 93/153
Installing : p11-kit-0.25.0-2.fc39.x86_64 94/153
Installing : libgomp-13.2.1-1.fc39.x86_64 95/153
Installing : libnghttp2-1.55.1-2.fc39.x86_64 96/153
Installing : libpkgconf-1.9.5-2.fc39.x86_64 97/153
Installing : pkgconf-1.9.5-2.fc39.x86_64 98/153
Installing : pkgconf-pkg-config-1.9.5-2.fc39.x86_64 99/153
Installing : libsigsegv-2.14-5.fc39.x86_64 100/153
Installing : gawk-5.2.2-2.fc39.x86_64 101/153
Installing : libtasn1-4.19.0-3.fc39.x86_64 102/153
Installing : p11-kit-trust-0.25.0-2.fc39.x86_64 103/153
Running scriptlet: p11-kit-trust-0.25.0-2.fc39.x86_64 103/153
Installing : libverto-0.3.2-6.fc39.x86_64 104/153
Installing : xxhash-libs-0.8.2-1.fc39.x86_64 105/153
Installing : libssh-config-0.10.5-2.fc39.noarch 106/153
Installing : kernel-srpm-macros-1.0-20.fc39.noarch 107/153
Installing : gnat-srpm-macros-6-3.fc39.noarch 108/153
Installing : ghc-srpm-macros-1.6.1-2.fc39.noarch 109/153
Installing : fpc-srpm-macros-1.3-8.fc39.noarch 110/153
Installing : coreutils-common-9.3-2.fc39.x86_64 111/153
Installing : openssl-libs-1:3.1.1-1.fc39.x86_64 112/153
Installing : coreutils-9.3-2.fc39.x86_64 113/153
Running scriptlet: ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch 114/153
Installing : ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch 114/153
Running scriptlet: ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch 114/153
Installing : krb5-libs-1.21-3.fc39.x86_64 115/153
Installing : libtirpc-1.3.3-1.rc2.fc39.x86_64 116/153
Running scriptlet: authselect-libs-1.4.2-3.fc39.x86_64 117/153
Installing : authselect-libs-1.4.2-3.fc39.x86_64 117/153
Installing : gzip-1.12-6.fc39.x86_64 118/153
Installing : cracklib-2.9.11-2.fc39.x86_64 119/153
Installing : libpwquality-1.4.5-6.fc39.x86_64 120/153
Installing : authselect-1.4.2-3.fc39.x86_64 121/153
Installing : libnsl2-2.0.0-6.fc39.x86_64 122/153
Installing : pam-1.5.3-2.fc39.x86_64 123/153
Installing : libssh-0.10.5-2.fc39.x86_64 124/153
Installing : libarchive-3.7.1-1.fc39.x86_64 125/153
Installing : libevent-2.1.12-9.fc39.x86_64 126/153
Installing : openldap-2.6.6-1.fc39.x86_64 127/153
Installing : libcurl-8.2.1-2.fc40.x86_64 128/153
Installing : elfutils-libs-0.189-4.fc39.x86_64 129/153
Installing : elfutils-debuginfod-client-0.189-4.fc39.x86_64 130/153
Installing : binutils-gold-2.40-13.fc39.x86_64 131/153
Running scriptlet: binutils-gold-2.40-13.fc39.x86_64 131/153
Installing : binutils-2.40-13.fc39.x86_64 132/153
Running scriptlet: binutils-2.40-13.fc39.x86_64 132/153
Installing : elfutils-0.189-4.fc39.x86_64 133/153
Installing : gdb-minimal-13.2-7.fc39.x86_64 134/153
Installing : debugedit-5.0-10.fc39.x86_64 135/153
Installing : curl-8.2.1-2.fc40.x86_64 136/153
Installing : rpm-sequoia-1.4.1-2.fc39.x86_64 137/153
Installing : rpm-libs-4.18.92-1.fc39.x86_64 138/153
Running scriptlet: rpm-4.18.92-1.fc39.x86_64 139/153
Installing : rpm-4.18.92-1.fc39.x86_64 139/153
Installing : efi-srpm-macros-5-9.fc39.noarch 140/153
Installing : lua-srpm-macros-1-9.fc39.noarch 141/153
Installing : rpmautospec-rpm-macros-0.3.5-4.fc39.noarch 142/153
Installing : rpm-build-libs-4.18.92-1.fc39.x86_64 143/153
Installing : ansible-srpm-macros-1-11.fc39.noarch 144/153
Installing : pyproject-srpm-macros-1.9.0-2.fc40.noarch 145/153
Installing : fonts-srpm-macros-1:2.0.5-12.fc39.noarch 146/153
Installing : go-srpm-macros-3.2.0-6.fc39.noarch 147/153
Installing : python-srpm-macros-3.12-2.fc39.noarch 148/153
Installing : redhat-rpm-config-262-1.fc39.noarch 149/153
Installing : rpm-build-4.18.92-1.fc39.x86_64 150/153
Installing : util-linux-2.39.1-3.fc39.x86_64 151/153
Installing : which-2.21-40.fc39.x86_64 152/153
Installing : info-7.0.3-3.fc39.x86_64 153/153
Running scriptlet: filesystem-3.18-6.fc39.x86_64 153/153
Running scriptlet: ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch 153/153
Running scriptlet: authselect-libs-1.4.2-3.fc39.x86_64 153/153
Running scriptlet: rpm-4.18.92-1.fc39.x86_64 153/153
Running scriptlet: info-7.0.3-3.fc39.x86_64 153/153
Verifying : libselinux-3.5-5.fc40.x86_64 1/153
Verifying : pyproject-srpm-macros-1.9.0-2.fc40.noarch 2/153
Verifying : alternatives-1.25-1.fc39.x86_64 3/153
Verifying : ansible-srpm-macros-1-11.fc39.noarch 4/153
Verifying : audit-libs-3.1.2-1.fc39.x86_64 5/153
Verifying : authselect-1.4.2-3.fc39.x86_64 6/153
Verifying : authselect-libs-1.4.2-3.fc39.x86_64 7/153
Verifying : basesystem-11-18.fc39.noarch 8/153
Verifying : bash-5.2.15-5.fc39.x86_64 9/153
Verifying : binutils-2.40-13.fc39.x86_64 10/153
Verifying : binutils-gold-2.40-13.fc39.x86_64 11/153
Verifying : bzip2-1.0.8-16.fc39.x86_64 12/153
Verifying : bzip2-libs-1.0.8-16.fc39.x86_64 13/153
Verifying : ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch 14/153
Verifying : coreutils-9.3-2.fc39.x86_64 15/153
Verifying : coreutils-common-9.3-2.fc39.x86_64 16/153
Verifying : cpio-2.14-4.fc39.x86_64 17/153
Verifying : cracklib-2.9.11-2.fc39.x86_64 18/153
Verifying : crypto-policies-20230731-1.git5ed06e0.fc39.noarc 19/153
Verifying : curl-8.2.1-2.fc40.x86_64 20/153
Verifying : cyrus-sasl-lib-2.1.28-11.fc39.x86_64 21/153
Verifying : debugedit-5.0-10.fc39.x86_64 22/153
Verifying : diffutils-3.10-3.fc39.x86_64 23/153
Verifying : dwz-0.15-3.fc39.x86_64 24/153
Verifying : ed-1.19-4.fc39.x86_64 25/153
Verifying : efi-srpm-macros-5-9.fc39.noarch 26/153
Verifying : elfutils-0.189-4.fc39.x86_64 27/153
Verifying : elfutils-debuginfod-client-0.189-4.fc39.x86_64 28/153
Verifying : elfutils-default-yama-scope-0.189-4.fc39.noarch 29/153
Verifying : elfutils-libelf-0.189-4.fc39.x86_64 30/153
Verifying : elfutils-libs-0.189-4.fc39.x86_64 31/153
Verifying : fedora-gpg-keys-40-0.1.noarch 32/153
Verifying : fedora-release-40-0.2.noarch 33/153
Verifying : fedora-release-common-40-0.2.noarch 34/153
Verifying : fedora-release-identity-basic-40-0.2.noarch 35/153
Verifying : fedora-repos-40-0.1.noarch 36/153
Verifying : fedora-repos-rawhide-40-0.1.noarch 37/153
Verifying : file-5.44-5.fc39.x86_64 38/153
Verifying : file-libs-5.44-5.fc39.x86_64 39/153
Verifying : filesystem-3.18-6.fc39.x86_64 40/153
Verifying : findutils-1:4.9.0-5.fc39.x86_64 41/153
Verifying : fonts-srpm-macros-1:2.0.5-12.fc39.noarch 42/153
Verifying : fpc-srpm-macros-1.3-8.fc39.noarch 43/153
Verifying : gawk-5.2.2-2.fc39.x86_64 44/153
Verifying : gdb-minimal-13.2-7.fc39.x86_64 45/153
Verifying : gdbm-libs-1:1.23-4.fc39.x86_64 46/153
Verifying : ghc-srpm-macros-1.6.1-2.fc39.noarch 47/153
Verifying : glibc-2.38-1.fc39.x86_64 48/153
Verifying : glibc-common-2.38-1.fc39.x86_64 49/153
Verifying : glibc-gconv-extra-2.38-1.fc39.x86_64 50/153
Verifying : glibc-minimal-langpack-2.38-1.fc39.x86_64 51/153
Verifying : gmp-1:6.2.1-5.fc39.x86_64 52/153
Verifying : gnat-srpm-macros-6-3.fc39.noarch 53/153
Verifying : go-srpm-macros-3.2.0-6.fc39.noarch 54/153
Verifying : grep-3.11-5.fc40.x86_64 55/153
Verifying : gzip-1.12-6.fc39.x86_64 56/153
Verifying : info-7.0.3-3.fc39.x86_64 57/153
Verifying : jansson-2.13.1-7.fc39.x86_64 58/153
Verifying : kernel-srpm-macros-1.0-20.fc39.noarch 59/153
Verifying : keyutils-libs-1.6.1-7.fc39.x86_64 60/153
Verifying : krb5-libs-1.21-3.fc39.x86_64 61/153
Verifying : libacl-2.3.1-8.fc39.x86_64 62/153
Verifying : libarchive-3.7.1-1.fc39.x86_64 63/153
Verifying : libattr-2.5.1-8.fc39.x86_64 64/153
Verifying : libblkid-2.39.1-3.fc39.x86_64 65/153
Verifying : libbrotli-1.0.9-13.fc39.x86_64 66/153
Verifying : libcap-2.48-7.fc39.x86_64 67/153
Verifying : libcap-ng-0.8.3-7.fc39.x86_64 68/153
Verifying : libcom_err-1.47.0-2.fc39.x86_64 69/153
Verifying : libcurl-8.2.1-2.fc40.x86_64 70/153
Verifying : libdb-5.3.28-56.fc39.x86_64 71/153
Verifying : libeconf-0.4.0-6.fc39.x86_64 72/153
Verifying : libevent-2.1.12-9.fc39.x86_64 73/153
Verifying : libfdisk-2.39.1-3.fc39.x86_64 74/153
Verifying : libffi-3.4.4-4.fc39.x86_64 75/153
Verifying : libgcc-13.2.1-1.fc39.x86_64 76/153
Verifying : libgomp-13.2.1-1.fc39.x86_64 77/153
Verifying : libidn2-2.3.4-3.fc39.x86_64 78/153
Verifying : libmount-2.39.1-3.fc39.x86_64 79/153
Verifying : libnghttp2-1.55.1-2.fc39.x86_64 80/153
Verifying : libnsl2-2.0.0-6.fc39.x86_64 81/153
Verifying : libpkgconf-1.9.5-2.fc39.x86_64 82/153
Verifying : libpsl-0.21.2-4.fc39.x86_64 83/153
Verifying : libpwquality-1.4.5-6.fc39.x86_64 84/153
Verifying : libsemanage-3.5-4.fc39.x86_64 85/153
Verifying : libsepol-3.5-2.fc39.x86_64 86/153
Verifying : libsigsegv-2.14-5.fc39.x86_64 87/153
Verifying : libsmartcols-2.39.1-3.fc39.x86_64 88/153
Verifying : libssh-0.10.5-2.fc39.x86_64 89/153
Verifying : libssh-config-0.10.5-2.fc39.noarch 90/153
Verifying : libstdc++-13.2.1-1.fc39.x86_64 91/153
Verifying : libtasn1-4.19.0-3.fc39.x86_64 92/153
Verifying : libtirpc-1.3.3-1.rc2.fc39.x86_64 93/153
Verifying : libunistring-1.1-4.fc39.x86_64 94/153
Verifying : libutempter-1.2.1-10.fc39.x86_64 95/153
Verifying : libuuid-2.39.1-3.fc39.x86_64 96/153
Verifying : libverto-0.3.2-6.fc39.x86_64 97/153
Verifying : libxcrypt-4.4.36-2.fc39.x86_64 98/153
Verifying : libxml2-2.10.4-3.fc39.x86_64 99/153
Verifying : libzstd-1.5.5-4.fc39.x86_64 100/153
Verifying : lua-libs-5.4.6-3.fc39.x86_64 101/153
Verifying : lua-srpm-macros-1-9.fc39.noarch 102/153
Verifying : lz4-libs-1.9.4-4.fc39.x86_64 103/153
Verifying : mpfr-4.2.0-3.fc39.x86_64 104/153
Verifying : ncurses-base-6.4-6.20230520.fc39.noarch 105/153
Verifying : ncurses-libs-6.4-6.20230520.fc39.x86_64 106/153
Verifying : ocaml-srpm-macros-8-2.fc39.noarch 107/153
Verifying : openblas-srpm-macros-2-14.fc39.noarch 108/153
Verifying : openldap-2.6.6-1.fc39.x86_64 109/153
Verifying : openssl-libs-1:3.1.1-1.fc39.x86_64 110/153
Verifying : p11-kit-0.25.0-2.fc39.x86_64 111/153
Verifying : p11-kit-trust-0.25.0-2.fc39.x86_64 112/153
Verifying : package-notes-srpm-macros-0.5-9.fc39.noarch 113/153
Verifying : pam-1.5.3-2.fc39.x86_64 114/153
Verifying : pam-libs-1.5.3-2.fc39.x86_64 115/153
Verifying : patch-2.7.6-22.fc39.x86_64 116/153
Verifying : pcre2-10.42-1.fc39.2.x86_64 117/153
Verifying : pcre2-syntax-10.42-1.fc39.2.noarch 118/153
Verifying : perl-srpm-macros-1-51.fc39.noarch 119/153
Verifying : pkgconf-1.9.5-2.fc39.x86_64 120/153
Verifying : pkgconf-m4-1.9.5-2.fc39.noarch 121/153
Verifying : pkgconf-pkg-config-1.9.5-2.fc39.x86_64 122/153
Verifying : popt-1.19-3.fc39.x86_64 123/153
Verifying : publicsuffix-list-dafsa-20230614-2.fc39.noarch 124/153
Verifying : python-srpm-macros-3.12-2.fc39.noarch 125/153
Verifying : qt5-srpm-macros-5.15.10-2.fc39.noarch 126/153
Verifying : qt6-srpm-macros-6.5.2-2.fc39.noarch 127/153
Verifying : readline-8.2-4.fc39.x86_64 128/153
Verifying : redhat-rpm-config-262-1.fc39.noarch 129/153
Verifying : rpm-4.18.92-1.fc39.x86_64 130/153
Verifying : rpm-build-4.18.92-1.fc39.x86_64 131/153
Verifying : rpm-build-libs-4.18.92-1.fc39.x86_64 132/153
Verifying : rpm-libs-4.18.92-1.fc39.x86_64 133/153
Verifying : rpm-sequoia-1.4.1-2.fc39.x86_64 134/153
Verifying : rpmautospec-rpm-macros-0.3.5-4.fc39.noarch 135/153
Verifying : rust-srpm-macros-24-3.fc39.noarch 136/153
Verifying : sed-4.8-14.fc39.x86_64 137/153
Verifying : setup-2.14.4-1.fc39.noarch 138/153
Verifying : shadow-utils-2:4.13-8.fc39.x86_64 139/153
Verifying : sqlite-libs-3.42.0-7.fc39.x86_64 140/153
Verifying : systemd-libs-254.1-2.fc40.x86_64 141/153
Verifying : tar-2:1.35-1.fc39.x86_64 142/153
Verifying : tzdata-2023c-2.fc39.noarch 143/153
Verifying : unzip-6.0-62.fc39.x86_64 144/153
Verifying : util-linux-2.39.1-3.fc39.x86_64 145/153
Verifying : util-linux-core-2.39.1-3.fc39.x86_64 146/153
Verifying : which-2.21-40.fc39.x86_64 147/153
Verifying : xxhash-libs-0.8.2-1.fc39.x86_64 148/153
Verifying : xz-5.4.4-1.fc39.x86_64 149/153
Verifying : xz-libs-5.4.4-1.fc39.x86_64 150/153
Verifying : zip-3.0-38.fc39.x86_64 151/153
Verifying : zlib-1.2.13-4.fc39.x86_64 152/153
Verifying : zstd-1.5.5-4.fc39.x86_64 153/153
Installed:
alternatives-1.25-1.fc39.x86_64
ansible-srpm-macros-1-11.fc39.noarch
audit-libs-3.1.2-1.fc39.x86_64
authselect-1.4.2-3.fc39.x86_64
authselect-libs-1.4.2-3.fc39.x86_64
basesystem-11-18.fc39.noarch
bash-5.2.15-5.fc39.x86_64
binutils-2.40-13.fc39.x86_64
binutils-gold-2.40-13.fc39.x86_64
bzip2-1.0.8-16.fc39.x86_64
bzip2-libs-1.0.8-16.fc39.x86_64
ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch
coreutils-9.3-2.fc39.x86_64
coreutils-common-9.3-2.fc39.x86_64
cpio-2.14-4.fc39.x86_64
cracklib-2.9.11-2.fc39.x86_64
crypto-policies-20230731-1.git5ed06e0.fc39.noarch
curl-8.2.1-2.fc40.x86_64
cyrus-sasl-lib-2.1.28-11.fc39.x86_64
debugedit-5.0-10.fc39.x86_64
diffutils-3.10-3.fc39.x86_64
dwz-0.15-3.fc39.x86_64
ed-1.19-4.fc39.x86_64
efi-srpm-macros-5-9.fc39.noarch
elfutils-0.189-4.fc39.x86_64
elfutils-debuginfod-client-0.189-4.fc39.x86_64
elfutils-default-yama-scope-0.189-4.fc39.noarch
elfutils-libelf-0.189-4.fc39.x86_64
elfutils-libs-0.189-4.fc39.x86_64
fedora-gpg-keys-40-0.1.noarch
fedora-release-40-0.2.noarch
fedora-release-common-40-0.2.noarch
fedora-release-identity-basic-40-0.2.noarch
fedora-repos-40-0.1.noarch
fedora-repos-rawhide-40-0.1.noarch
file-5.44-5.fc39.x86_64
file-libs-5.44-5.fc39.x86_64
filesystem-3.18-6.fc39.x86_64
findutils-1:4.9.0-5.fc39.x86_64
fonts-srpm-macros-1:2.0.5-12.fc39.noarch
fpc-srpm-macros-1.3-8.fc39.noarch
gawk-5.2.2-2.fc39.x86_64
gdb-minimal-13.2-7.fc39.x86_64
gdbm-libs-1:1.23-4.fc39.x86_64
ghc-srpm-macros-1.6.1-2.fc39.noarch
glibc-2.38-1.fc39.x86_64
glibc-common-2.38-1.fc39.x86_64
glibc-gconv-extra-2.38-1.fc39.x86_64
glibc-minimal-langpack-2.38-1.fc39.x86_64
gmp-1:6.2.1-5.fc39.x86_64
gnat-srpm-macros-6-3.fc39.noarch
go-srpm-macros-3.2.0-6.fc39.noarch
grep-3.11-5.fc40.x86_64
gzip-1.12-6.fc39.x86_64
info-7.0.3-3.fc39.x86_64
jansson-2.13.1-7.fc39.x86_64
kernel-srpm-macros-1.0-20.fc39.noarch
keyutils-libs-1.6.1-7.fc39.x86_64
krb5-libs-1.21-3.fc39.x86_64
libacl-2.3.1-8.fc39.x86_64
libarchive-3.7.1-1.fc39.x86_64
libattr-2.5.1-8.fc39.x86_64
libblkid-2.39.1-3.fc39.x86_64
libbrotli-1.0.9-13.fc39.x86_64
libcap-2.48-7.fc39.x86_64
libcap-ng-0.8.3-7.fc39.x86_64
libcom_err-1.47.0-2.fc39.x86_64
libcurl-8.2.1-2.fc40.x86_64
libdb-5.3.28-56.fc39.x86_64
libeconf-0.4.0-6.fc39.x86_64
libevent-2.1.12-9.fc39.x86_64
libfdisk-2.39.1-3.fc39.x86_64
libffi-3.4.4-4.fc39.x86_64
libgcc-13.2.1-1.fc39.x86_64
libgomp-13.2.1-1.fc39.x86_64
libidn2-2.3.4-3.fc39.x86_64
libmount-2.39.1-3.fc39.x86_64
libnghttp2-1.55.1-2.fc39.x86_64
libnsl2-2.0.0-6.fc39.x86_64
libpkgconf-1.9.5-2.fc39.x86_64
libpsl-0.21.2-4.fc39.x86_64
libpwquality-1.4.5-6.fc39.x86_64
libselinux-3.5-5.fc40.x86_64
libsemanage-3.5-4.fc39.x86_64
libsepol-3.5-2.fc39.x86_64
libsigsegv-2.14-5.fc39.x86_64
libsmartcols-2.39.1-3.fc39.x86_64
libssh-0.10.5-2.fc39.x86_64
libssh-config-0.10.5-2.fc39.noarch
libstdc++-13.2.1-1.fc39.x86_64
libtasn1-4.19.0-3.fc39.x86_64
libtirpc-1.3.3-1.rc2.fc39.x86_64
libunistring-1.1-4.fc39.x86_64
libutempter-1.2.1-10.fc39.x86_64
libuuid-2.39.1-3.fc39.x86_64
libverto-0.3.2-6.fc39.x86_64
libxcrypt-4.4.36-2.fc39.x86_64
libxml2-2.10.4-3.fc39.x86_64
libzstd-1.5.5-4.fc39.x86_64
lua-libs-5.4.6-3.fc39.x86_64
lua-srpm-macros-1-9.fc39.noarch
lz4-libs-1.9.4-4.fc39.x86_64
mpfr-4.2.0-3.fc39.x86_64
ncurses-base-6.4-6.20230520.fc39.noarch
ncurses-libs-6.4-6.20230520.fc39.x86_64
ocaml-srpm-macros-8-2.fc39.noarch
openblas-srpm-macros-2-14.fc39.noarch
openldap-2.6.6-1.fc39.x86_64
openssl-libs-1:3.1.1-1.fc39.x86_64
p11-kit-0.25.0-2.fc39.x86_64
p11-kit-trust-0.25.0-2.fc39.x86_64
package-notes-srpm-macros-0.5-9.fc39.noarch
pam-1.5.3-2.fc39.x86_64
pam-libs-1.5.3-2.fc39.x86_64
patch-2.7.6-22.fc39.x86_64
pcre2-10.42-1.fc39.2.x86_64
pcre2-syntax-10.42-1.fc39.2.noarch
perl-srpm-macros-1-51.fc39.noarch
pkgconf-1.9.5-2.fc39.x86_64
pkgconf-m4-1.9.5-2.fc39.noarch
pkgconf-pkg-config-1.9.5-2.fc39.x86_64
popt-1.19-3.fc39.x86_64
publicsuffix-list-dafsa-20230614-2.fc39.noarch
pyproject-srpm-macros-1.9.0-2.fc40.noarch
python-srpm-macros-3.12-2.fc39.noarch
qt5-srpm-macros-5.15.10-2.fc39.noarch
qt6-srpm-macros-6.5.2-2.fc39.noarch
readline-8.2-4.fc39.x86_64
redhat-rpm-config-262-1.fc39.noarch
rpm-4.18.92-1.fc39.x86_64
rpm-build-4.18.92-1.fc39.x86_64
rpm-build-libs-4.18.92-1.fc39.x86_64
rpm-libs-4.18.92-1.fc39.x86_64
rpm-sequoia-1.4.1-2.fc39.x86_64
rpmautospec-rpm-macros-0.3.5-4.fc39.noarch
rust-srpm-macros-24-3.fc39.noarch
sed-4.8-14.fc39.x86_64
setup-2.14.4-1.fc39.noarch
shadow-utils-2:4.13-8.fc39.x86_64
sqlite-libs-3.42.0-7.fc39.x86_64
systemd-libs-254.1-2.fc40.x86_64
tar-2:1.35-1.fc39.x86_64
tzdata-2023c-2.fc39.noarch
unzip-6.0-62.fc39.x86_64
util-linux-2.39.1-3.fc39.x86_64
util-linux-core-2.39.1-3.fc39.x86_64
which-2.21-40.fc39.x86_64
xxhash-libs-0.8.2-1.fc39.x86_64
xz-5.4.4-1.fc39.x86_64
xz-libs-5.4.4-1.fc39.x86_64
zip-3.0-38.fc39.x86_64
zlib-1.2.13-4.fc39.x86_64
zstd-1.5.5-4.fc39.x86_64
Complete!
Finish: installing minimal buildroot with dnf
Start: creating root cache
Finish: creating root cache
Finish: chroot init
INFO: Installed packages:
INFO: gmp-6.2.1-5.fc39.x86_64
publicsuffix-list-dafsa-20230614-2.fc39.noarch
fedora-release-identity-basic-40-0.2.noarch
fedora-repos-rawhide-40-0.1.noarch
binutils-2.40-13.fc39.x86_64
unzip-6.0-62.fc39.x86_64
kernel-srpm-macros-1.0-20.fc39.noarch
libssh-0.10.5-2.fc39.x86_64
fedora-release-common-40-0.2.noarch
sed-4.8-14.fc39.x86_64
ed-1.19-4.fc39.x86_64
libgomp-13.2.1-1.fc39.x86_64
pyproject-srpm-macros-1.9.0-2.fc40.noarch
ghc-srpm-macros-1.6.1-2.fc39.noarch
package-notes-srpm-macros-0.5-9.fc39.noarch
go-srpm-macros-3.2.0-6.fc39.noarch
diffutils-3.10-3.fc39.x86_64
p11-kit-0.25.0-2.fc39.x86_64
systemd-libs-254.1-2.fc40.x86_64
libzstd-1.5.5-4.fc39.x86_64
elfutils-libelf-0.189-4.fc39.x86_64
libsepol-3.5-2.fc39.x86_64
libffi-3.4.4-4.fc39.x86_64
tzdata-2023c-2.fc39.noarch
readline-8.2-4.fc39.x86_64
glibc-2.38-1.fc39.x86_64
dwz-0.15-3.fc39.x86_64
gdb-minimal-13.2-7.fc39.x86_64
rpm-sequoia-1.4.1-2.fc39.x86_64
libuuid-2.39.1-3.fc39.x86_64
qt6-srpm-macros-6.5.2-2.fc39.noarch
perl-srpm-macros-1-51.fc39.noarch
libacl-2.3.1-8.fc39.x86_64
gzip-1.12-6.fc39.x86_64
lua-srpm-macros-1-9.fc39.noarch
file-libs-5.44-5.fc39.x86_64
rpm-libs-4.18.92-1.fc39.x86_64
libssh-config-0.10.5-2.fc39.noarch
rpm-4.18.92-1.fc39.x86_64
libverto-0.3.2-6.fc39.x86_64
elfutils-libs-0.189-4.fc39.x86_64
filesystem-3.18-6.fc39.x86_64
gawk-5.2.2-2.fc39.x86_64
bzip2-1.0.8-16.fc39.x86_64
libeconf-0.4.0-6.fc39.x86_64
libutempter-1.2.1-10.fc39.x86_64
libcap-2.48-7.fc39.x86_64
fpc-srpm-macros-1.3-8.fc39.noarch
setup-2.14.4-1.fc39.noarch
bzip2-libs-1.0.8-16.fc39.x86_64
libnsl2-2.0.0-6.fc39.x86_64
libfdisk-2.39.1-3.fc39.x86_64
pkgconf-pkg-config-1.9.5-2.fc39.x86_64
ocaml-srpm-macros-8-2.fc39.noarch
popt-1.19-3.fc39.x86_64
xz-5.4.4-1.fc39.x86_64
glibc-minimal-langpack-2.38-1.fc39.x86_64
file-5.44-5.fc39.x86_64
libstdc++-13.2.1-1.fc39.x86_64
libtirpc-1.3.3-1.rc2.fc39.x86_64
fonts-srpm-macros-2.0.5-12.fc39.noarch
util-linux-core-2.39.1-3.fc39.x86_64
libtasn1-4.19.0-3.fc39.x86_64
qt5-srpm-macros-5.15.10-2.fc39.noarch
fedora-release-40-0.2.noarch
mpfr-4.2.0-3.fc39.x86_64
debugedit-5.0-10.fc39.x86_64
zlib-1.2.13-4.fc39.x86_64
libdb-5.3.28-56.fc39.x86_64
elfutils-debuginfod-client-0.189-4.fc39.x86_64
jansson-2.13.1-7.fc39.x86_64
efi-srpm-macros-5-9.fc39.noarch
libbrotli-1.0.9-13.fc39.x86_64
xz-libs-5.4.4-1.fc39.x86_64
libcurl-8.2.1-2.fc40.x86_64
gpg-pubkey-a15b79cc-63d04c2c
shadow-utils-4.13-8.fc39.x86_64
gdbm-libs-1.23-4.fc39.x86_64
openblas-srpm-macros-2-14.fc39.noarch
libpkgconf-1.9.5-2.fc39.x86_64
alternatives-1.25-1.fc39.x86_64
libgcc-13.2.1-1.fc39.x86_64
cyrus-sasl-lib-2.1.28-11.fc39.x86_64
keyutils-libs-1.6.1-7.fc39.x86_64
authselect-libs-1.4.2-3.fc39.x86_64
grep-3.11-5.fc40.x86_64
p11-kit-trust-0.25.0-2.fc39.x86_64
python-srpm-macros-3.12-2.fc39.noarch
libnghttp2-1.55.1-2.fc39.x86_64
lz4-libs-1.9.4-4.fc39.x86_64
cpio-2.14-4.fc39.x86_64
libunistring-1.1-4.fc39.x86_64
libarchive-3.7.1-1.fc39.x86_64
gnat-srpm-macros-6-3.fc39.noarch
libxcrypt-4.4.36-2.fc39.x86_64
rpm-build-libs-4.18.92-1.fc39.x86_64
lua-libs-5.4.6-3.fc39.x86_64
ansible-srpm-macros-1-11.fc39.noarch
xxhash-libs-0.8.2-1.fc39.x86_64
libxml2-2.10.4-3.fc39.x86_64
openssl-libs-3.1.1-1.fc39.x86_64
libselinux-3.5-5.fc40.x86_64
elfutils-default-yama-scope-0.189-4.fc39.noarch
zip-3.0-38.fc39.x86_64
gpg-pubkey-18b8e74c-62f2920f
audit-libs-3.1.2-1.fc39.x86_64
authselect-1.4.2-3.fc39.x86_64
libblkid-2.39.1-3.fc39.x86_64
info-7.0.3-3.fc39.x86_64
ca-certificates-2023.2.60_v7.0.306-2.fc39.noarch
libcap-ng-0.8.3-7.fc39.x86_64
ncurses-libs-6.4-6.20230520.fc39.x86_64
pcre2-syntax-10.42-1.fc39.2.noarch
libattr-2.5.1-8.fc39.x86_64
rpmautospec-rpm-macros-0.3.5-4.fc39.noarch
libsemanage-3.5-4.fc39.x86_64
coreutils-common-9.3-2.fc39.x86_64
glibc-common-2.38-1.fc39.x86_64
zstd-1.5.5-4.fc39.x86_64
pam-1.5.3-2.fc39.x86_64
patch-2.7.6-22.fc39.x86_64
bash-5.2.15-5.fc39.x86_64
fedora-repos-40-0.1.noarch
tar-1.35-1.fc39.x86_64
pkgconf-m4-1.9.5-2.fc39.noarch
ncurses-base-6.4-6.20230520.fc39.noarch
pcre2-10.42-1.fc39.2.x86_64
util-linux-2.39.1-3.fc39.x86_64
pkgconf-1.9.5-2.fc39.x86_64
findutils-4.9.0-5.fc39.x86_64
redhat-rpm-config-262-1.fc39.noarch
fedora-gpg-keys-40-0.1.noarch
libmount-2.39.1-3.fc39.x86_64
elfutils-0.189-4.fc39.x86_64
libpsl-0.21.2-4.fc39.x86_64
basesystem-11-18.fc39.noarch
rust-srpm-macros-24-3.fc39.noarch
openldap-2.6.6-1.fc39.x86_64
glibc-gconv-extra-2.38-1.fc39.x86_64
sqlite-libs-3.42.0-7.fc39.x86_64
binutils-gold-2.40-13.fc39.x86_64
pam-libs-1.5.3-2.fc39.x86_64
libsmartcols-2.39.1-3.fc39.x86_64
libpwquality-1.4.5-6.fc39.x86_64
coreutils-9.3-2.fc39.x86_64
libidn2-2.3.4-3.fc39.x86_64
cracklib-2.9.11-2.fc39.x86_64
rpm-build-4.18.92-1.fc39.x86_64
libsigsegv-2.14-5.fc39.x86_64
which-2.21-40.fc39.x86_64
krb5-libs-1.21-3.fc39.x86_64
libevent-2.1.12-9.fc39.x86_64
crypto-policies-20230731-1.git5ed06e0.fc39.noarch
curl-8.2.1-2.fc40.x86_64
libcom_err-1.47.0-2.fc39.x86_64
Start: buildsrpm
Start: rpmbuild -bs
error: %changelog not in descending chronological order
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1689724800
Wrote: /builddir/build/SRPMS/python-django-4.2.3-1.fc40.src.rpm
Finish: rpmbuild -bs
INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root/var/log/dnf.rpm.log
/var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root/var/log/dnf.librepo.log
/var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root/var/log/dnf.log
Finish: buildsrpm
INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-59i6v6pc/python-django/python-django.spec) Config(child) 0 minutes 38 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
Finish: run
Running (timeout=18000): unbuffer mock --rebuild /var/lib/copr-rpmbuild/results/python-django-4.2.3-1.fc40.src.rpm --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1692096785.491105 -r /var/lib/copr-rpmbuild/results/configs/child.cfg
INFO: mock.py version 5.0 starting (python version = 3.11.3, NVR = mock-5.0-1.fc38)...
Start(bootstrap): init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish(bootstrap): init plugins
Start: init plugins
INFO: tmpfs initialized
INFO: selinux enabled
INFO: chroot_scan: initialized
INFO: compress_logs: initialized
Finish: init plugins
INFO: Signal handler active
Start: run
INFO: Start(/var/lib/copr-rpmbuild/results/python-django-4.2.3-1.fc40.src.rpm) Config(fedora-rawhide-x86_64)
Start: clean chroot
Finish: clean chroot
Mock Version: 5.0
INFO: Mock Version: 5.0
Start(bootstrap): chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1692096785.491105/root.
INFO: reusing tmpfs at /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1692096785.491105/root.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled package manager cache
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Package manager dnf detected and used (fallback)
Finish(bootstrap): chroot init
Start: chroot init
INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root.
INFO: calling preinit hooks
INFO: enabled root cache
Start: unpacking root cache
Finish: unpacking root cache
INFO: enabled package manager cache
Start: cleaning package manager metadata
Finish: cleaning package manager metadata
INFO: enabled HW Info plugin
INFO: Package manager dnf detected and used (direct choice)
Start: dnf update
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 92 kB/s | 1.5 kB 00:00
Copr repository 46 MB/s | 1.7 MB 00:00
fedora 71 kB/s | 22 kB 00:00
Dependencies resolved.
Nothing to do.
Complete!
Finish: dnf update
Finish: chroot init
Start: build phase for python-django-4.2.3-1.fc40.src.rpm
Start: build setup for python-django-4.2.3-1.fc40.src.rpm
error: %changelog not in descending chronological order
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1689724800
Wrote: /builddir/build/SRPMS/python-django-4.2.3-1.fc40.src.rpm
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 89 kB/s | 1.5 kB 00:00
fedora 81 kB/s | 22 kB 00:00
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
bash-completion noarch 1:2.11-12.fc39 fedora 367 k
make x86_64 1:4.4.1-2.fc39 fedora 589 k
python3-asgiref noarch 3.6.0-4.fc40 copr_base 54 k
python3-devel x86_64 3.12.0~rc1-1.fc40 fedora 311 k
Installing dependencies:
expat x86_64 2.5.0-3.fc39 fedora 110 k
gc x86_64 8.2.2-4.fc39 fedora 110 k
guile22 x86_64 2.2.7-9.fc39 fedora 6.5 M
libb2 x86_64 0.98.1-9.fc39 fedora 25 k
libtool-ltdl x86_64 2.4.7-7.fc39 fedora 36 k
mpdecimal x86_64 2.5.1-7.fc39 fedora 89 k
pyproject-rpm-macros noarch 1.9.0-2.fc40 copr_base 42 k
python-pip-wheel noarch 23.2.1-1.fc40 copr_base 1.5 M
python-rpm-macros noarch 3.12-2.fc39 fedora 19 k
python3 x86_64 3.12.0~rc1-1.fc40 fedora 26 k
python3-libs x86_64 3.12.0~rc1-1.fc40 fedora 9.2 M
python3-packaging noarch 23.1-4.fc39 fedora 114 k
python3-rpm-generators noarch 14-7.fc39 fedora 30 k
python3-rpm-macros noarch 3.12-2.fc39 fedora 14 k
Transaction Summary
================================================================================
Install 18 Packages
Total size: 19 M
Total download size: 422 k
Installed size: 92 M
Downloading Packages:
[SKIPPED] pyproject-rpm-macros-1.9.0-2.fc40.noarch.rpm: Already downloaded
[SKIPPED] python-pip-wheel-23.2.1-1.fc40.noarch.rpm: Already downloaded
[SKIPPED] expat-2.5.0-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] gc-8.2.2-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] guile22-2.2.7-9.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libb2-0.98.1-9.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libtool-ltdl-2.4.7-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] make-4.4.1-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] mpdecimal-2.5.1-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] python-rpm-macros-3.12-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-3.12.0~rc1-1.fc40.x86_64.rpm: Already downloaded
[SKIPPED] python3-devel-3.12.0~rc1-1.fc40.x86_64.rpm: Already downloaded
[SKIPPED] python3-libs-3.12.0~rc1-1.fc40.x86_64.rpm: Already downloaded
[SKIPPED] python3-packaging-23.1-4.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-rpm-generators-14-7.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-rpm-macros-3.12-2.fc39.noarch.rpm: Already downloaded
(17/18): python3-asgiref-3.6.0-4.fc40.noarch.rp 3.7 MB/s | 54 kB 00:00
(18/18): bash-completion-2.11-12.fc39.noarch.rp 12 MB/s | 367 kB 00:00
--------------------------------------------------------------------------------
Total 3.5 MB/s | 422 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : python-rpm-macros-3.12-2.fc39.noarch 1/18
Installing : python3-rpm-macros-3.12-2.fc39.noarch 2/18
Installing : pyproject-rpm-macros-1.9.0-2.fc40.noarch 3/18
Installing : mpdecimal-2.5.1-7.fc39.x86_64 4/18
Installing : libtool-ltdl-2.4.7-7.fc39.x86_64 5/18
Installing : libb2-0.98.1-9.fc39.x86_64 6/18
Installing : gc-8.2.2-4.fc39.x86_64 7/18
Installing : guile22-2.2.7-9.fc39.x86_64 8/18
Installing : expat-2.5.0-3.fc39.x86_64 9/18
Installing : python-pip-wheel-23.2.1-1.fc40.noarch 10/18
Installing : python3-3.12.0~rc1-1.fc40.x86_64 11/18
Installing : python3-libs-3.12.0~rc1-1.fc40.x86_64 12/18
Installing : python3-packaging-23.1-4.fc39.noarch 13/18
Installing : python3-rpm-generators-14-7.fc39.noarch 14/18
Installing : python3-devel-3.12.0~rc1-1.fc40.x86_64 15/18
Installing : python3-asgiref-3.6.0-4.fc40.noarch 16/18
Installing : make-1:4.4.1-2.fc39.x86_64 17/18
Installing : bash-completion-1:2.11-12.fc39.noarch 18/18
Running scriptlet: bash-completion-1:2.11-12.fc39.noarch 18/18
Verifying : pyproject-rpm-macros-1.9.0-2.fc40.noarch 1/18
Verifying : python-pip-wheel-23.2.1-1.fc40.noarch 2/18
Verifying : python3-asgiref-3.6.0-4.fc40.noarch 3/18
Verifying : bash-completion-1:2.11-12.fc39.noarch 4/18
Verifying : expat-2.5.0-3.fc39.x86_64 5/18
Verifying : gc-8.2.2-4.fc39.x86_64 6/18
Verifying : guile22-2.2.7-9.fc39.x86_64 7/18
Verifying : libb2-0.98.1-9.fc39.x86_64 8/18
Verifying : libtool-ltdl-2.4.7-7.fc39.x86_64 9/18
Verifying : make-1:4.4.1-2.fc39.x86_64 10/18
Verifying : mpdecimal-2.5.1-7.fc39.x86_64 11/18
Verifying : python-rpm-macros-3.12-2.fc39.noarch 12/18
Verifying : python3-3.12.0~rc1-1.fc40.x86_64 13/18
Verifying : python3-devel-3.12.0~rc1-1.fc40.x86_64 14/18
Verifying : python3-libs-3.12.0~rc1-1.fc40.x86_64 15/18
Verifying : python3-packaging-23.1-4.fc39.noarch 16/18
Verifying : python3-rpm-generators-14-7.fc39.noarch 17/18
Verifying : python3-rpm-macros-3.12-2.fc39.noarch 18/18
Installed:
bash-completion-1:2.11-12.fc39.noarch
expat-2.5.0-3.fc39.x86_64
gc-8.2.2-4.fc39.x86_64
guile22-2.2.7-9.fc39.x86_64
libb2-0.98.1-9.fc39.x86_64
libtool-ltdl-2.4.7-7.fc39.x86_64
make-1:4.4.1-2.fc39.x86_64
mpdecimal-2.5.1-7.fc39.x86_64
pyproject-rpm-macros-1.9.0-2.fc40.noarch
python-pip-wheel-23.2.1-1.fc40.noarch
python-rpm-macros-3.12-2.fc39.noarch
python3-3.12.0~rc1-1.fc40.x86_64
python3-asgiref-3.6.0-4.fc40.noarch
python3-devel-3.12.0~rc1-1.fc40.x86_64
python3-libs-3.12.0~rc1-1.fc40.x86_64
python3-packaging-23.1-4.fc39.noarch
python3-rpm-generators-14-7.fc39.noarch
python3-rpm-macros-3.12-2.fc39.noarch
Complete!
Finish: build setup for python-django-4.2.3-1.fc40.src.rpm
Start: rpmbuild python-django-4.2.3-1.fc40.src.rpm
error: %changelog not in descending chronological order
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1689724800
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.GxaZg7
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf Django-4.2.3
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/Django-4.2.3.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd Django-4.2.3
+ rm -rf /builddir/build/BUILD/Django-4.2.3-SPECPARTS
+ /usr/bin/mkdir -p /builddir/build/BUILD/Django-4.2.3-SPECPARTS
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/dirty-hack-remove-assert.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ pushd django
~/build/BUILD/Django-4.2.3/django ~/build/BUILD/Django-4.2.3
+ for file in conf/project_template/manage.py-tpl
+ sed -i 's/\/env python/\/python3/' conf/project_template/manage.py-tpl
+ popd
~/build/BUILD/Django-4.2.3
+ sed -i 's/psycopg\[binary\]>=3\.1\.8/psycopg>=3.1.8/' tests/requirements/postgres.txt
+ sed -i '/^pywatchman\b/d' tests/requirements/py3.txt
+ sed -i '/^tzdata$/d' tests/requirements/py3.txt
+ sed -i '/^black\b/d' tests/requirements/py3.txt
+ sed -i '/^blacken-docs\b/d' docs/requirements.txt
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.N7eDlv
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ TMPDIR=/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ RPM_TOXENV=py312
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir --output /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires -r tests/requirements/py3.txt tests/requirements/postgres.txt tests/requirements/mysql.txt tests/requirements/oracle.txt docs/requirements.txt
Handling aiosmtpd from requirements file tests/requirements/py3.txt
Requirement not satisfied: aiosmtpd
Handling asgiref >= 3.6.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: asgiref >= 3.6.0
(installed: asgiref 3.6.0)
Handling argon2-cffi >= 19.2.0 from requirements file tests/requirements/py3.txt
Requirement not satisfied: argon2-cffi >= 19.2.0
Handling backports.zoneinfo; python_version < '3.9' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: backports.zoneinfo; python_version < '3.9'
Handling bcrypt from requirements file tests/requirements/py3.txt
Requirement not satisfied: bcrypt
Handling docutils from requirements file tests/requirements/py3.txt
Requirement not satisfied: docutils
Handling geoip2; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: geoip2; python_version < '3.12'
Handling jinja2 >= 2.11.0 from requirements file tests/requirements/py3.txt
Requirement not satisfied: jinja2 >= 2.11.0
Handling numpy; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: numpy; python_version < '3.12'
Handling Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12' from requirements file tests/requirements/py3.txt
Requirement not satisfied: Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12'
Handling pylibmc; sys.platform != 'win32' from requirements file tests/requirements/py3.txt
Requirement not satisfied: pylibmc; sys.platform != 'win32'
Handling pymemcache >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement not satisfied: pymemcache >= 3.4.0
Handling pytz from requirements file tests/requirements/py3.txt
Requirement not satisfied: pytz
Handling PyYAML from requirements file tests/requirements/py3.txt
Requirement not satisfied: PyYAML
Handling redis >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement not satisfied: redis >= 3.4.0
Handling selenium >= 3.8.0 from requirements file tests/requirements/py3.txt
Requirement not satisfied: selenium >= 3.8.0
Handling sqlparse >= 0.3.1 from requirements file tests/requirements/py3.txt
Requirement not satisfied: sqlparse >= 0.3.1
Handling tblib >= 1.5.0 from requirements file tests/requirements/py3.txt
Requirement not satisfied: tblib >= 1.5.0
Handling colorama; sys.platform == 'win32' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: colorama; sys.platform == 'win32'
Handling psycopg>=3.1.8 from requirements file tests/requirements/postgres.txt
Requirement not satisfied: psycopg>=3.1.8
Handling mysqlclient >= 1.4.3 from requirements file tests/requirements/mysql.txt
Requirement not satisfied: mysqlclient >= 1.4.3
Handling cx_oracle >= 7.0 from requirements file tests/requirements/oracle.txt
Requirement not satisfied: cx_oracle >= 7.0
Handling pyenchant from requirements file docs/requirements.txt
Requirement not satisfied: pyenchant
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement not satisfied: Sphinx>=4.5.0
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement not satisfied: sphinxcontrib-spelling
Exiting dependency generation pass: all requirements files
+ cat /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires
+ rm -rfv '*.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-django-4.2.3-1.fc40.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 64 kB/s | 1.5 kB 00:00
fedora 246 kB/s | 22 kB 00:00
Package bash-completion-1:2.11-12.fc39.noarch is already installed.
Package make-1:4.4.1-2.fc39.x86_64 is already installed.
Package pyproject-rpm-macros-1.9.0-2.fc40.noarch is already installed.
Package python3-asgiref-3.6.0-4.fc40.noarch is already installed.
Package python3-devel-3.12.0~rc1-1.fc40.x86_64 is already installed.
Package python3-devel-3.12.0~rc1-1.fc40.x86_64 is already installed.
Package python3-asgiref-3.6.0-4.fc40.noarch is already installed.
Package python3-packaging-23.1-4.fc39.noarch is already installed.
Dependencies resolved.
=========================================================================================
Package Arch Version Repo Size
=========================================================================================
Installing:
python3-aiosmtpd noarch 1.4.4.post2-6.fc40 copr_base 304 k
python3-argon2-cffi noarch 21.3.0-4.fc39 fedora 38 k
python3-bcrypt x86_64 4.0.1-5.fc40 copr_base 221 k
python3-cx-oracle x86_64 8.3.0-5.fc40 copr_base 185 k
python3-docutils noarch 0.20.1-1.fc40 fedora 1.0 M
python3-enchant noarch 3.2.2-9.fc39 fedora 100 k
python3-jinja2 noarch 3.1.2-5.fc39 fedora 506 k
python3-mysqlclient x86_64 2.1.1-5.fc39 fedora 104 k
python3-pillow x86_64 10.0.0-2.fc39 fedora 914 k
python3-pip noarch 23.2.1-1.fc40 copr_base 2.9 M
python3-psycopg3 noarch 3.1.10-1.fc39 fedora 409 k
python3-pylibmc x86_64 1.6.3-4.fc39 fedora 84 k
python3-pymemcache noarch 3.5.0-8.fc39 fedora 148 k
python3-pytz noarch 2023.3-3.fc39 fedora 64 k
python3-pyyaml x86_64 6.0.1-12.fc40 copr_base 219 k
python3-redis noarch 4.5.1-3.fc39 fedora 501 k
python3-selenium noarch 3.141.0-4.fc39 fedora 914 k
python3-sphinx noarch 1:7.0.1-1.fc40 copr_base 2.4 M
python3-sphinxcontrib-spelling noarch 7.3.3-6.fc39 fedora 40 k
python3-sqlparse noarch 0.4.2-7.fc39 fedora 117 k
python3-tblib noarch 2.0.0-4.fc39 fedora 27 k
Installing dependencies:
abattis-cantarell-vf-fonts noarch 0.301-10.fc39 fedora 121 k
cairo x86_64 1.17.8-5.fc39 fedora 705 k
default-fonts-core-sans noarch 4.0-8.fc40 fedora 32 k
enchant2 x86_64 2.5.0-5.fc39 fedora 62 k
fontconfig x86_64 2.14.2-4.fc39 fedora 296 k
fonts-filesystem noarch 1:2.0.5-12.fc39 fedora 8.2 k
freetype x86_64 2.13.1-2.fc39 fedora 414 k
fribidi x86_64 1.0.13-2.fc39 fedora 91 k
glib2 x86_64 2.77.2-1.fc40 fedora 2.8 M
gnutls x86_64 3.8.0-7.fc39 fedora 1.1 M
google-noto-fonts-common noarch 20230801-2.fc40 fedora 17 k
google-noto-sans-vf-fonts noarch 20230801-2.fc40 fedora 583 k
graphite2 x86_64 1.3.14-12.fc39 fedora 95 k
harfbuzz x86_64 8.1.1-1.fc39 fedora 949 k
hunspell x86_64 1.7.2-5.fc39 fedora 472 k
hunspell-en-US noarch 0.20201207-7.fc39 fedora 181 k
hunspell-filesystem x86_64 1.7.2-5.fc39 fedora 9.2 k
jbigkit-libs x86_64 2.1-26.fc39 fedora 53 k
lcms2 x86_64 2.15-2.fc39 fedora 177 k
libX11 x86_64 1.8.6-2.fc39 fedora 649 k
libX11-common noarch 1.8.6-2.fc39 fedora 175 k
libXau x86_64 1.0.11-3.fc39 fedora 31 k
libXext x86_64 1.3.5-3.fc39 fedora 39 k
libXrender x86_64 0.9.11-3.fc39 fedora 27 k
libargon2 x86_64 20190702-3.fc39 fedora 28 k
libimagequant x86_64 4.0.1-5.fc39 fedora 308 k
libjpeg-turbo x86_64 2.1.4-3.fc39 fedora 183 k
libmemcached-awesome x86_64 1.1.4-2.fc39 fedora 112 k
libpng x86_64 2:1.6.37-15.fc39 fedora 119 k
libpq x86_64 15.3-1.fc39 fedora 215 k
libraqm x86_64 0.8.0-5.fc39 fedora 20 k
libtiff x86_64 4.4.0-7.fc39 fedora 197 k
libwebp x86_64 1.3.1-2.fc39 fedora 284 k
libxcb x86_64 1.13.1-12.fc39 fedora 233 k
libyaml x86_64 0.2.5-12.fc39 fedora 59 k
mariadb-connector-c x86_64 3.3.5-2.fc39 fedora 208 k
mariadb-connector-c-config noarch 3.3.5-2.fc39 fedora 8.8 k
nettle x86_64 3.9.1-2.fc39 fedora 425 k
openjpeg2 x86_64 2.5.0-4.fc39 fedora 178 k
pixman x86_64 0.42.2-2.fc39 fedora 288 k
python3-argon2-cffi-bindings x86_64 21.2.0-4.fc40 copr_base 27 k
python3-async-timeout noarch 4.0.2-9.fc40 copr_base 20 k
python3-atpublic x86_64 3.1.1-4.fc39 fedora 29 k
python3-attrs noarch 23.1.0-4.fc39 fedora 123 k
python3-babel noarch 2.12.1-4.fc39~bootstrap fedora 6.9 M
python3-cffi x86_64 1.15.1-6.fc39 fedora 307 k
python3-charset-normalizer noarch 3.2.0-2.fc40 copr_base 97 k
python3-idna noarch 3.4-4.fc39 fedora 109 k
python3-imagesize noarch 1.4.1-4.fc39 fedora 22 k
python3-isodate noarch 0.6.1-9.fc39 fedora 77 k
python3-markupsafe x86_64 2.1.3-2.fc39 fedora 30 k
python3-olefile noarch 0.46-21.fc39 fedora 66 k
python3-ply noarch 3.11-20.fc39 fedora 135 k
python3-pycparser noarch 2.20-11.fc39 fedora 153 k
python3-pygments noarch 2.15.1-4.fc39 fedora 2.4 M
python3-pyparsing noarch 3.0.9-11.fc39 fedora 254 k
python3-pysocks noarch 1.7.1-20.fc39 fedora 39 k
python3-rdflib noarch 6.2.0-4.fc39 fedora 940 k
python3-requests noarch 2.28.2-5.fc39 fedora 152 k
python3-setuptools noarch 67.7.2-5.fc39 fedora 1.5 M
python3-six noarch 1.16.0-12.fc39 fedora 41 k
python3-snowballstemmer noarch 2.2.0-7.fc39 fedora 257 k
python3-sphinx-theme-alabaster noarch 0.7.12-19.fc39 fedora 29 k
python3-sphinxcontrib-applehelp noarch 1.0.6-1.fc40 fedora 45 k
python3-sphinxcontrib-devhelp noarch 1.0.2-14.fc39 fedora 41 k
python3-sphinxcontrib-htmlhelp noarch 2.0.3-1.fc40 fedora 54 k
python3-sphinxcontrib-jsmath noarch 1.0.1-22.fc39 fedora 17 k
python3-sphinxcontrib-qthelp noarch 1.0.3-15.fc39 fedora 47 k
python3-sphinxcontrib-serializinghtml noarch 1.1.5-10.fc39 fedora 47 k
python3-typing-extensions noarch 4.7.1-2.fc40 copr_base 79 k
python3-urllib3 noarch 1.26.16-2.fc39 fedora 253 k
python3-urllib3+socks noarch 1.26.16-2.fc39 fedora 9.9 k
xml-common noarch 0.6.3-61.fc39 fedora 31 k
Transaction Summary
=========================================================================================
Install 94 Packages
Total size: 37 M
Total download size: 5.6 M
Installed size: 145 M
Downloading Packages:
[SKIPPED] python3-charset-normalizer-3.2.0-2.fc40.noarch.rpm: Already downloaded
[SKIPPED] python3-pip-23.2.1-1.fc40.noarch.rpm: Already downloaded
[SKIPPED] python3-pyyaml-6.0.1-12.fc40.x86_64.rpm: Already downloaded
[SKIPPED] python3-sphinx-7.0.1-1.fc40.noarch.rpm: Already downloaded
[SKIPPED] python3-typing-extensions-4.7.1-2.fc40.noarch.rpm: Already downloaded
[SKIPPED] abattis-cantarell-vf-fonts-0.301-10.fc39.noarch.rpm: Already downloaded
[SKIPPED] cairo-1.17.8-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] default-fonts-core-sans-4.0-8.fc40.noarch.rpm: Already downloaded
[SKIPPED] fontconfig-2.14.2-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] fonts-filesystem-2.0.5-12.fc39.noarch.rpm: Already downloaded
[SKIPPED] freetype-2.13.1-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] fribidi-1.0.13-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] glib2-2.77.2-1.fc40.x86_64.rpm: Already downloaded
[SKIPPED] gnutls-3.8.0-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] google-noto-fonts-common-20230801-2.fc40.noarch.rpm: Already downloaded
[SKIPPED] google-noto-sans-vf-fonts-20230801-2.fc40.noarch.rpm: Already downloaded
[SKIPPED] graphite2-1.3.14-12.fc39.x86_64.rpm: Already downloaded
[SKIPPED] harfbuzz-8.1.1-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] jbigkit-libs-2.1-26.fc39.x86_64.rpm: Already downloaded
[SKIPPED] lcms2-2.15-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libX11-1.8.6-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libX11-common-1.8.6-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] libXau-1.0.11-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libXext-1.3.5-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libXrender-0.9.11-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libimagequant-4.0.1-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libjpeg-turbo-2.1.4-3.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libpng-1.6.37-15.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libpq-15.3-1.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libraqm-0.8.0-5.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libtiff-4.4.0-7.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libwebp-1.3.1-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libxcb-1.13.1-12.fc39.x86_64.rpm: Already downloaded
[SKIPPED] libyaml-0.2.5-12.fc39.x86_64.rpm: Already downloaded
[SKIPPED] mariadb-connector-c-3.3.5-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] mariadb-connector-c-config-3.3.5-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] nettle-3.9.1-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] openjpeg2-2.5.0-4.fc39.x86_64.rpm: Already downloaded
[SKIPPED] pixman-0.42.2-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] python3-attrs-23.1.0-4.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-babel-2.12.1-4.fc39~bootstrap.noarch.rpm: Already downloaded
[SKIPPED] python3-docutils-0.20.1-1.fc40.noarch.rpm: Already downloaded
[SKIPPED] python3-idna-3.4-4.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-imagesize-1.4.1-4.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-jinja2-3.1.2-5.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-markupsafe-2.1.3-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] python3-olefile-0.46-21.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-pillow-10.0.0-2.fc39.x86_64.rpm: Already downloaded
[SKIPPED] python3-pygments-2.15.1-4.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-pyparsing-3.0.9-11.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-pysocks-1.7.1-20.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-pytz-2023.3-3.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-requests-2.28.2-5.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-setuptools-67.7.2-5.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-six-1.16.0-12.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-snowballstemmer-2.2.0-7.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-sphinx-theme-alabaster-0.7.12-19.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-sphinxcontrib-applehelp-1.0.6-1.fc40.noarch.rpm: Already downloaded
[SKIPPED] python3-sphinxcontrib-devhelp-1.0.2-14.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-sphinxcontrib-htmlhelp-2.0.3-1.fc40.noarch.rpm: Already downloaded
[SKIPPED] python3-sphinxcontrib-jsmath-1.0.1-22.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-sphinxcontrib-qthelp-1.0.3-15.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-sphinxcontrib-serializinghtml-1.1.5-10.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-urllib3+socks-1.26.16-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] python3-urllib3-1.26.16-2.fc39.noarch.rpm: Already downloaded
[SKIPPED] xml-common-0.6.3-61.fc39.noarch.rpm: Already downloaded
(67/94): python3-async-timeout-4.0.2-9.fc40.noa 1.1 MB/s | 20 kB 00:00
(68/94): python3-bcrypt-4.0.1-5.fc40.x86_64.rpm 54 MB/s | 221 kB 00:00
(69/94): python3-argon2-cffi-bindings-21.2.0-4. 885 kB/s | 27 kB 00:00
(70/94): python3-cx-oracle-8.3.0-5.fc40.x86_64. 11 MB/s | 185 kB 00:00
(71/94): enchant2-2.5.0-5.fc39.x86_64.rpm 8.9 MB/s | 62 kB 00:00
(72/94): hunspell-1.7.2-5.fc39.x86_64.rpm 77 MB/s | 472 kB 00:00
(73/94): hunspell-en-US-0.20201207-7.fc39.noarc 29 MB/s | 181 kB 00:00
(74/94): hunspell-filesystem-1.7.2-5.fc39.x86_6 5.1 MB/s | 9.2 kB 00:00
(75/94): libargon2-20190702-3.fc39.x86_64.rpm 12 MB/s | 28 kB 00:00
(76/94): python3-argon2-cffi-21.3.0-4.fc39.noar 15 MB/s | 38 kB 00:00
(77/94): python3-atpublic-3.1.1-4.fc39.x86_64.r 3.7 MB/s | 29 kB 00:00
(78/94): python3-cffi-1.15.1-6.fc39.x86_64.rpm 125 MB/s | 307 kB 00:00
(79/94): libmemcached-awesome-1.1.4-2.fc39.x86_ 7.3 MB/s | 112 kB 00:00
(80/94): python3-enchant-3.2.2-9.fc39.noarch.rp 36 MB/s | 100 kB 00:00
(81/94): python3-isodate-0.6.1-9.fc39.noarch.rp 35 MB/s | 77 kB 00:00
(82/94): python3-ply-3.11-20.fc39.noarch.rpm 58 MB/s | 135 kB 00:00
(83/94): python3-psycopg3-3.1.10-1.fc39.noarch. 76 MB/s | 409 kB 00:00
(84/94): python3-mysqlclient-2.1.1-5.fc39.x86_6 11 MB/s | 104 kB 00:00
(85/94): python3-aiosmtpd-1.4.4.post2-6.fc40.no 4.0 MB/s | 304 kB 00:00
(86/94): python3-pycparser-2.20-11.fc39.noarch. 55 MB/s | 153 kB 00:00
(87/94): python3-pylibmc-1.6.3-4.fc39.x86_64.rp 5.4 MB/s | 84 kB 00:00
(88/94): python3-rdflib-6.2.0-4.fc39.noarch.rpm 58 MB/s | 940 kB 00:00
(89/94): python3-pymemcache-3.5.0-8.fc39.noarch 6.9 MB/s | 148 kB 00:00
(90/94): python3-sphinxcontrib-spelling-7.3.3-6 10 MB/s | 40 kB 00:00
(91/94): python3-sqlparse-0.4.2-7.fc39.noarch.r 62 MB/s | 117 kB 00:00
(92/94): python3-tblib-2.0.0-4.fc39.noarch.rpm 2.5 MB/s | 27 kB 00:00
(93/94): python3-redis-4.5.1-3.fc39.noarch.rpm 16 MB/s | 501 kB 00:00
(94/94): python3-selenium-3.141.0-4.fc39.noarch 24 MB/s | 914 kB 00:00
--------------------------------------------------------------------------------
Total 12 MB/s | 5.6 MB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : python3-six-1.16.0-12.fc39.noarch 1/94
Installing : python3-setuptools-67.7.2-5.fc39.noarch 2/94
Installing : fonts-filesystem-1:2.0.5-12.fc39.noarch 3/94
Installing : python3-idna-3.4-4.fc39.noarch 4/94
Installing : libwebp-1.3.1-2.fc39.x86_64 5/94
Installing : libpng-2:1.6.37-15.fc39.x86_64 6/94
Installing : libjpeg-turbo-2.1.4-3.fc39.x86_64 7/94
Installing : hunspell-filesystem-1.7.2-5.fc39.x86_64 8/94
Installing : hunspell-en-US-0.20201207-7.fc39.noarch 9/94
Installing : hunspell-1.7.2-5.fc39.x86_64 10/94
Installing : abattis-cantarell-vf-fonts-0.301-10.fc39.noarch 11/94
Installing : python3-atpublic-3.1.1-4.fc39.x86_64 12/94
Installing : python3-isodate-0.6.1-9.fc39.noarch 13/94
Running scriptlet: xml-common-0.6.3-61.fc39.noarch 14/94
Installing : xml-common-0.6.3-61.fc39.noarch 14/94
Installing : python3-sphinxcontrib-serializinghtml-1.1.5-10.fc3 15/94
Installing : python3-sphinxcontrib-qthelp-1.0.3-15.fc39.noarch 16/94
Installing : python3-sphinxcontrib-jsmath-1.0.1-22.fc39.noarch 17/94
Installing : python3-sphinxcontrib-devhelp-1.0.2-14.fc39.noarch 18/94
Installing : python3-sphinx-theme-alabaster-0.7.12-19.fc39.noar 19/94
Installing : python3-snowballstemmer-2.2.0-7.fc39.noarch 20/94
Installing : python3-pysocks-1.7.1-20.fc39.noarch 21/94
Installing : python3-urllib3+socks-1.26.16-2.fc39.noarch 22/94
Installing : python3-urllib3-1.26.16-2.fc39.noarch 23/94
Installing : python3-pyparsing-3.0.9-11.fc39.noarch 24/94
Installing : python3-rdflib-6.2.0-4.fc39.noarch 25/94
Installing : python3-pygments-2.15.1-4.fc39.noarch 26/94
Installing : python3-ply-3.11-20.fc39.noarch 27/94
Installing : python3-pycparser-2.20-11.fc39.noarch 28/94
Installing : python3-cffi-1.15.1-6.fc39.x86_64 29/94
Installing : python3-olefile-0.46-21.fc39.noarch 30/94
Installing : python3-markupsafe-2.1.3-2.fc39.x86_64 31/94
Installing : python3-jinja2-3.1.2-5.fc39.noarch 32/94
Installing : python3-imagesize-1.4.1-4.fc39.noarch 33/94
Installing : python3-docutils-0.20.1-1.fc40.noarch 34/94
Installing : python3-babel-2.12.1-4.fc39~bootstrap.noarch 35/94
Installing : python3-attrs-23.1.0-4.fc39.noarch 36/94
Installing : pixman-0.42.2-2.fc39.x86_64 37/94
Installing : openjpeg2-2.5.0-4.fc39.x86_64 38/94
Installing : nettle-3.9.1-2.fc39.x86_64 39/94
Installing : gnutls-3.8.0-7.fc39.x86_64 40/94
Installing : glib2-2.77.2-1.fc40.x86_64 41/94
Installing : enchant2-2.5.0-5.fc39.x86_64 42/94
Installing : python3-enchant-3.2.2-9.fc39.noarch 43/94
Installing : mariadb-connector-c-config-3.3.5-2.fc39.noarch 44/94
Installing : mariadb-connector-c-3.3.5-2.fc39.x86_64 45/94
Installing : libyaml-0.2.5-12.fc39.x86_64 46/94
Installing : libpq-15.3-1.fc39.x86_64 47/94
Installing : libmemcached-awesome-1.1.4-2.fc39.x86_64 48/94
Installing : libimagequant-4.0.1-5.fc39.x86_64 49/94
Installing : libargon2-20190702-3.fc39.x86_64 50/94
Installing : python3-argon2-cffi-bindings-21.2.0-4.fc40.x86_64 51/94
Installing : libXau-1.0.11-3.fc39.x86_64 52/94
Installing : libxcb-1.13.1-12.fc39.x86_64 53/94
Installing : libX11-common-1.8.6-2.fc39.noarch 54/94
Installing : libX11-1.8.6-2.fc39.x86_64 55/94
Installing : libXext-1.3.5-3.fc39.x86_64 56/94
Installing : libXrender-0.9.11-3.fc39.x86_64 57/94
Installing : lcms2-2.15-2.fc39.x86_64 58/94
Installing : jbigkit-libs-2.1-26.fc39.x86_64 59/94
Installing : libtiff-4.4.0-7.fc39.x86_64 60/94
Installing : graphite2-1.3.14-12.fc39.x86_64 61/94
Installing : google-noto-fonts-common-20230801-2.fc40.noarch 62/94
Installing : google-noto-sans-vf-fonts-20230801-2.fc40.noarch 63/94
Installing : default-fonts-core-sans-4.0-8.fc40.noarch 64/94
Installing : cairo-1.17.8-5.fc39.x86_64 65/94
Installing : harfbuzz-8.1.1-1.fc39.x86_64 66/94
Installing : freetype-2.13.1-2.fc39.x86_64 67/94
Installing : fontconfig-2.14.2-4.fc39.x86_64 68/94
Running scriptlet: fontconfig-2.14.2-4.fc39.x86_64 68/94
Installing : fribidi-1.0.13-2.fc39.x86_64 69/94
Installing : libraqm-0.8.0-5.fc39.x86_64 70/94
Installing : python3-typing-extensions-4.7.1-2.fc40.noarch 71/94
Installing : python3-charset-normalizer-3.2.0-2.fc40.noarch 72/94
Installing : python3-requests-2.28.2-5.fc39.noarch 73/94
Installing : python3-sphinxcontrib-applehelp-1.0.6-1.fc40.noarc 74/94
Installing : python3-sphinxcontrib-htmlhelp-2.0.3-1.fc40.noarch 75/94
Installing : python3-sphinx-1:7.0.1-1.fc40.noarch 76/94
Installing : python3-async-timeout-4.0.2-9.fc40.noarch 77/94
Installing : python3-redis-4.5.1-3.fc39.noarch 78/94
Installing : python3-sphinxcontrib-spelling-7.3.3-6.fc39.noarch 79/94
Installing : python3-psycopg3-3.1.10-1.fc39.noarch 80/94
Installing : python3-pillow-10.0.0-2.fc39.x86_64 81/94
Installing : python3-argon2-cffi-21.3.0-4.fc39.noarch 82/94
Installing : python3-pylibmc-1.6.3-4.fc39.x86_64 83/94
Installing : python3-pyyaml-6.0.1-12.fc40.x86_64 84/94
Installing : python3-mysqlclient-2.1.1-5.fc39.x86_64 85/94
Installing : python3-aiosmtpd-1.4.4.post2-6.fc40.noarch 86/94
Installing : python3-selenium-3.141.0-4.fc39.noarch 87/94
Installing : python3-pip-23.2.1-1.fc40.noarch 88/94
Installing : python3-pymemcache-3.5.0-8.fc39.noarch 89/94
Installing : python3-tblib-2.0.0-4.fc39.noarch 90/94
Installing : python3-sqlparse-0.4.2-7.fc39.noarch 91/94
Installing : python3-pytz-2023.3-3.fc39.noarch 92/94
Installing : python3-cx-oracle-8.3.0-5.fc40.x86_64 93/94
Installing : python3-bcrypt-4.0.1-5.fc40.x86_64 94/94
Running scriptlet: fontconfig-2.14.2-4.fc39.x86_64 94/94
Running scriptlet: python3-bcrypt-4.0.1-5.fc40.x86_64 94/94
Verifying : python3-aiosmtpd-1.4.4.post2-6.fc40.noarch 1/94
Verifying : python3-argon2-cffi-bindings-21.2.0-4.fc40.x86_64 2/94
Verifying : python3-async-timeout-4.0.2-9.fc40.noarch 3/94
Verifying : python3-bcrypt-4.0.1-5.fc40.x86_64 4/94
Verifying : python3-charset-normalizer-3.2.0-2.fc40.noarch 5/94
Verifying : python3-cx-oracle-8.3.0-5.fc40.x86_64 6/94
Verifying : python3-pip-23.2.1-1.fc40.noarch 7/94
Verifying : python3-pyyaml-6.0.1-12.fc40.x86_64 8/94
Verifying : python3-sphinx-1:7.0.1-1.fc40.noarch 9/94
Verifying : python3-typing-extensions-4.7.1-2.fc40.noarch 10/94
Verifying : abattis-cantarell-vf-fonts-0.301-10.fc39.noarch 11/94
Verifying : cairo-1.17.8-5.fc39.x86_64 12/94
Verifying : default-fonts-core-sans-4.0-8.fc40.noarch 13/94
Verifying : enchant2-2.5.0-5.fc39.x86_64 14/94
Verifying : fontconfig-2.14.2-4.fc39.x86_64 15/94
Verifying : fonts-filesystem-1:2.0.5-12.fc39.noarch 16/94
Verifying : freetype-2.13.1-2.fc39.x86_64 17/94
Verifying : fribidi-1.0.13-2.fc39.x86_64 18/94
Verifying : glib2-2.77.2-1.fc40.x86_64 19/94
Verifying : gnutls-3.8.0-7.fc39.x86_64 20/94
Verifying : google-noto-fonts-common-20230801-2.fc40.noarch 21/94
Verifying : google-noto-sans-vf-fonts-20230801-2.fc40.noarch 22/94
Verifying : graphite2-1.3.14-12.fc39.x86_64 23/94
Verifying : harfbuzz-8.1.1-1.fc39.x86_64 24/94
Verifying : hunspell-1.7.2-5.fc39.x86_64 25/94
Verifying : hunspell-en-US-0.20201207-7.fc39.noarch 26/94
Verifying : hunspell-filesystem-1.7.2-5.fc39.x86_64 27/94
Verifying : jbigkit-libs-2.1-26.fc39.x86_64 28/94
Verifying : lcms2-2.15-2.fc39.x86_64 29/94
Verifying : libX11-1.8.6-2.fc39.x86_64 30/94
Verifying : libX11-common-1.8.6-2.fc39.noarch 31/94
Verifying : libXau-1.0.11-3.fc39.x86_64 32/94
Verifying : libXext-1.3.5-3.fc39.x86_64 33/94
Verifying : libXrender-0.9.11-3.fc39.x86_64 34/94
Verifying : libargon2-20190702-3.fc39.x86_64 35/94
Verifying : libimagequant-4.0.1-5.fc39.x86_64 36/94
Verifying : libjpeg-turbo-2.1.4-3.fc39.x86_64 37/94
Verifying : libmemcached-awesome-1.1.4-2.fc39.x86_64 38/94
Verifying : libpng-2:1.6.37-15.fc39.x86_64 39/94
Verifying : libpq-15.3-1.fc39.x86_64 40/94
Verifying : libraqm-0.8.0-5.fc39.x86_64 41/94
Verifying : libtiff-4.4.0-7.fc39.x86_64 42/94
Verifying : libwebp-1.3.1-2.fc39.x86_64 43/94
Verifying : libxcb-1.13.1-12.fc39.x86_64 44/94
Verifying : libyaml-0.2.5-12.fc39.x86_64 45/94
Verifying : mariadb-connector-c-3.3.5-2.fc39.x86_64 46/94
Verifying : mariadb-connector-c-config-3.3.5-2.fc39.noarch 47/94
Verifying : nettle-3.9.1-2.fc39.x86_64 48/94
Verifying : openjpeg2-2.5.0-4.fc39.x86_64 49/94
Verifying : pixman-0.42.2-2.fc39.x86_64 50/94
Verifying : python3-argon2-cffi-21.3.0-4.fc39.noarch 51/94
Verifying : python3-atpublic-3.1.1-4.fc39.x86_64 52/94
Verifying : python3-attrs-23.1.0-4.fc39.noarch 53/94
Verifying : python3-babel-2.12.1-4.fc39~bootstrap.noarch 54/94
Verifying : python3-cffi-1.15.1-6.fc39.x86_64 55/94
Verifying : python3-docutils-0.20.1-1.fc40.noarch 56/94
Verifying : python3-enchant-3.2.2-9.fc39.noarch 57/94
Verifying : python3-idna-3.4-4.fc39.noarch 58/94
Verifying : python3-imagesize-1.4.1-4.fc39.noarch 59/94
Verifying : python3-isodate-0.6.1-9.fc39.noarch 60/94
Verifying : python3-jinja2-3.1.2-5.fc39.noarch 61/94
Verifying : python3-markupsafe-2.1.3-2.fc39.x86_64 62/94
Verifying : python3-mysqlclient-2.1.1-5.fc39.x86_64 63/94
Verifying : python3-olefile-0.46-21.fc39.noarch 64/94
Verifying : python3-pillow-10.0.0-2.fc39.x86_64 65/94
Verifying : python3-ply-3.11-20.fc39.noarch 66/94
Verifying : python3-psycopg3-3.1.10-1.fc39.noarch 67/94
Verifying : python3-pycparser-2.20-11.fc39.noarch 68/94
Verifying : python3-pygments-2.15.1-4.fc39.noarch 69/94
Verifying : python3-pylibmc-1.6.3-4.fc39.x86_64 70/94
Verifying : python3-pymemcache-3.5.0-8.fc39.noarch 71/94
Verifying : python3-pyparsing-3.0.9-11.fc39.noarch 72/94
Verifying : python3-pysocks-1.7.1-20.fc39.noarch 73/94
Verifying : python3-pytz-2023.3-3.fc39.noarch 74/94
Verifying : python3-rdflib-6.2.0-4.fc39.noarch 75/94
Verifying : python3-redis-4.5.1-3.fc39.noarch 76/94
Verifying : python3-requests-2.28.2-5.fc39.noarch 77/94
Verifying : python3-selenium-3.141.0-4.fc39.noarch 78/94
Verifying : python3-setuptools-67.7.2-5.fc39.noarch 79/94
Verifying : python3-six-1.16.0-12.fc39.noarch 80/94
Verifying : python3-snowballstemmer-2.2.0-7.fc39.noarch 81/94
Verifying : python3-sphinx-theme-alabaster-0.7.12-19.fc39.noar 82/94
Verifying : python3-sphinxcontrib-applehelp-1.0.6-1.fc40.noarc 83/94
Verifying : python3-sphinxcontrib-devhelp-1.0.2-14.fc39.noarch 84/94
Verifying : python3-sphinxcontrib-htmlhelp-2.0.3-1.fc40.noarch 85/94
Verifying : python3-sphinxcontrib-jsmath-1.0.1-22.fc39.noarch 86/94
Verifying : python3-sphinxcontrib-qthelp-1.0.3-15.fc39.noarch 87/94
Verifying : python3-sphinxcontrib-serializinghtml-1.1.5-10.fc3 88/94
Verifying : python3-sphinxcontrib-spelling-7.3.3-6.fc39.noarch 89/94
Verifying : python3-sqlparse-0.4.2-7.fc39.noarch 90/94
Verifying : python3-tblib-2.0.0-4.fc39.noarch 91/94
Verifying : python3-urllib3+socks-1.26.16-2.fc39.noarch 92/94
Verifying : python3-urllib3-1.26.16-2.fc39.noarch 93/94
Verifying : xml-common-0.6.3-61.fc39.noarch 94/94
Installed:
abattis-cantarell-vf-fonts-0.301-10.fc39.noarch
cairo-1.17.8-5.fc39.x86_64
default-fonts-core-sans-4.0-8.fc40.noarch
enchant2-2.5.0-5.fc39.x86_64
fontconfig-2.14.2-4.fc39.x86_64
fonts-filesystem-1:2.0.5-12.fc39.noarch
freetype-2.13.1-2.fc39.x86_64
fribidi-1.0.13-2.fc39.x86_64
glib2-2.77.2-1.fc40.x86_64
gnutls-3.8.0-7.fc39.x86_64
google-noto-fonts-common-20230801-2.fc40.noarch
google-noto-sans-vf-fonts-20230801-2.fc40.noarch
graphite2-1.3.14-12.fc39.x86_64
harfbuzz-8.1.1-1.fc39.x86_64
hunspell-1.7.2-5.fc39.x86_64
hunspell-en-US-0.20201207-7.fc39.noarch
hunspell-filesystem-1.7.2-5.fc39.x86_64
jbigkit-libs-2.1-26.fc39.x86_64
lcms2-2.15-2.fc39.x86_64
libX11-1.8.6-2.fc39.x86_64
libX11-common-1.8.6-2.fc39.noarch
libXau-1.0.11-3.fc39.x86_64
libXext-1.3.5-3.fc39.x86_64
libXrender-0.9.11-3.fc39.x86_64
libargon2-20190702-3.fc39.x86_64
libimagequant-4.0.1-5.fc39.x86_64
libjpeg-turbo-2.1.4-3.fc39.x86_64
libmemcached-awesome-1.1.4-2.fc39.x86_64
libpng-2:1.6.37-15.fc39.x86_64
libpq-15.3-1.fc39.x86_64
libraqm-0.8.0-5.fc39.x86_64
libtiff-4.4.0-7.fc39.x86_64
libwebp-1.3.1-2.fc39.x86_64
libxcb-1.13.1-12.fc39.x86_64
libyaml-0.2.5-12.fc39.x86_64
mariadb-connector-c-3.3.5-2.fc39.x86_64
mariadb-connector-c-config-3.3.5-2.fc39.noarch
nettle-3.9.1-2.fc39.x86_64
openjpeg2-2.5.0-4.fc39.x86_64
pixman-0.42.2-2.fc39.x86_64
python3-aiosmtpd-1.4.4.post2-6.fc40.noarch
python3-argon2-cffi-21.3.0-4.fc39.noarch
python3-argon2-cffi-bindings-21.2.0-4.fc40.x86_64
python3-async-timeout-4.0.2-9.fc40.noarch
python3-atpublic-3.1.1-4.fc39.x86_64
python3-attrs-23.1.0-4.fc39.noarch
python3-babel-2.12.1-4.fc39~bootstrap.noarch
python3-bcrypt-4.0.1-5.fc40.x86_64
python3-cffi-1.15.1-6.fc39.x86_64
python3-charset-normalizer-3.2.0-2.fc40.noarch
python3-cx-oracle-8.3.0-5.fc40.x86_64
python3-docutils-0.20.1-1.fc40.noarch
python3-enchant-3.2.2-9.fc39.noarch
python3-idna-3.4-4.fc39.noarch
python3-imagesize-1.4.1-4.fc39.noarch
python3-isodate-0.6.1-9.fc39.noarch
python3-jinja2-3.1.2-5.fc39.noarch
python3-markupsafe-2.1.3-2.fc39.x86_64
python3-mysqlclient-2.1.1-5.fc39.x86_64
python3-olefile-0.46-21.fc39.noarch
python3-pillow-10.0.0-2.fc39.x86_64
python3-pip-23.2.1-1.fc40.noarch
python3-ply-3.11-20.fc39.noarch
python3-psycopg3-3.1.10-1.fc39.noarch
python3-pycparser-2.20-11.fc39.noarch
python3-pygments-2.15.1-4.fc39.noarch
python3-pylibmc-1.6.3-4.fc39.x86_64
python3-pymemcache-3.5.0-8.fc39.noarch
python3-pyparsing-3.0.9-11.fc39.noarch
python3-pysocks-1.7.1-20.fc39.noarch
python3-pytz-2023.3-3.fc39.noarch
python3-pyyaml-6.0.1-12.fc40.x86_64
python3-rdflib-6.2.0-4.fc39.noarch
python3-redis-4.5.1-3.fc39.noarch
python3-requests-2.28.2-5.fc39.noarch
python3-selenium-3.141.0-4.fc39.noarch
python3-setuptools-67.7.2-5.fc39.noarch
python3-six-1.16.0-12.fc39.noarch
python3-snowballstemmer-2.2.0-7.fc39.noarch
python3-sphinx-1:7.0.1-1.fc40.noarch
python3-sphinx-theme-alabaster-0.7.12-19.fc39.noarch
python3-sphinxcontrib-applehelp-1.0.6-1.fc40.noarch
python3-sphinxcontrib-devhelp-1.0.2-14.fc39.noarch
python3-sphinxcontrib-htmlhelp-2.0.3-1.fc40.noarch
python3-sphinxcontrib-jsmath-1.0.1-22.fc39.noarch
python3-sphinxcontrib-qthelp-1.0.3-15.fc39.noarch
python3-sphinxcontrib-serializinghtml-1.1.5-10.fc39.noarch
python3-sphinxcontrib-spelling-7.3.3-6.fc39.noarch
python3-sqlparse-0.4.2-7.fc39.noarch
python3-tblib-2.0.0-4.fc39.noarch
python3-typing-extensions-4.7.1-2.fc40.noarch
python3-urllib3-1.26.16-2.fc39.noarch
python3-urllib3+socks-1.26.16-2.fc39.noarch
xml-common-0.6.3-61.fc39.noarch
Complete!
error: %changelog not in descending chronological order
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1689724800
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.cUjoJr
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf Django-4.2.3
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/Django-4.2.3.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd Django-4.2.3
+ rm -rf /builddir/build/BUILD/Django-4.2.3-SPECPARTS
+ /usr/bin/mkdir -p /builddir/build/BUILD/Django-4.2.3-SPECPARTS
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/dirty-hack-remove-assert.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ pushd django
~/build/BUILD/Django-4.2.3/django ~/build/BUILD/Django-4.2.3
+ for file in conf/project_template/manage.py-tpl
+ sed -i 's/\/env python/\/python3/' conf/project_template/manage.py-tpl
+ popd
~/build/BUILD/Django-4.2.3
+ sed -i 's/psycopg\[binary\]>=3\.1\.8/psycopg>=3.1.8/' tests/requirements/postgres.txt
+ sed -i '/^pywatchman\b/d' tests/requirements/py3.txt
+ sed -i '/^tzdata$/d' tests/requirements/py3.txt
+ sed -i '/^black\b/d' tests/requirements/py3.txt
+ sed -i '/^blacken-docs\b/d' docs/requirements.txt
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.iDzfy3
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ TMPDIR=/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ RPM_TOXENV=py312
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir --output /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires -r tests/requirements/py3.txt tests/requirements/postgres.txt tests/requirements/mysql.txt tests/requirements/oracle.txt docs/requirements.txt
Handling aiosmtpd from requirements file tests/requirements/py3.txt
Requirement satisfied: aiosmtpd
(installed: aiosmtpd 1.4.4.post2)
Handling asgiref >= 3.6.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: asgiref >= 3.6.0
(installed: asgiref 3.6.0)
Handling argon2-cffi >= 19.2.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: argon2-cffi >= 19.2.0
(installed: argon2-cffi 21.3.0)
Handling backports.zoneinfo; python_version < '3.9' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: backports.zoneinfo; python_version < '3.9'
Handling bcrypt from requirements file tests/requirements/py3.txt
Requirement satisfied: bcrypt
(installed: bcrypt 4.0.1)
Handling docutils from requirements file tests/requirements/py3.txt
Requirement satisfied: docutils
(installed: docutils 0.20.1)
Handling geoip2; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: geoip2; python_version < '3.12'
Handling jinja2 >= 2.11.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: jinja2 >= 2.11.0
(installed: jinja2 3.1.2)
Handling numpy; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: numpy; python_version < '3.12'
Handling Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12' from requirements file tests/requirements/py3.txt
Requirement satisfied: Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12'
(installed: Pillow 10.0.0)
Handling pylibmc; sys.platform != 'win32' from requirements file tests/requirements/py3.txt
Requirement satisfied: pylibmc; sys.platform != 'win32'
(installed: pylibmc 1.6.3)
Handling pymemcache >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: pymemcache >= 3.4.0
(installed: pymemcache 3.5.0)
Handling pytz from requirements file tests/requirements/py3.txt
Requirement satisfied: pytz
(installed: pytz 2023.3)
Handling PyYAML from requirements file tests/requirements/py3.txt
Requirement satisfied: PyYAML
(installed: PyYAML 6.0.1)
Handling redis >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: redis >= 3.4.0
(installed: redis 4.5.1)
Handling selenium >= 3.8.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: selenium >= 3.8.0
(installed: selenium 3.141.0)
Handling sqlparse >= 0.3.1 from requirements file tests/requirements/py3.txt
Requirement satisfied: sqlparse >= 0.3.1
(installed: sqlparse 0.4.2)
Handling tblib >= 1.5.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: tblib >= 1.5.0
(installed: tblib 2.0.0)
Handling colorama; sys.platform == 'win32' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: colorama; sys.platform == 'win32'
Handling psycopg>=3.1.8 from requirements file tests/requirements/postgres.txt
Requirement satisfied: psycopg>=3.1.8
(installed: psycopg 3.1.10)
Handling mysqlclient >= 1.4.3 from requirements file tests/requirements/mysql.txt
Requirement satisfied: mysqlclient >= 1.4.3
(installed: mysqlclient 2.1.1)
Handling cx_oracle >= 7.0 from requirements file tests/requirements/oracle.txt
Requirement satisfied: cx_oracle >= 7.0
(installed: cx_oracle 8.3.0)
Handling pyenchant from requirements file docs/requirements.txt
Requirement satisfied: pyenchant
(installed: pyenchant 3.2.2)
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement satisfied: Sphinx>=4.5.0
(installed: Sphinx 7.0.1)
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement satisfied: sphinxcontrib-spelling
(installed: sphinxcontrib-spelling 7.3.3)
Handling setuptools>=40.8.0 from build-system.requires
Requirement satisfied: setuptools>=40.8.0
(installed: setuptools 67.7.2)
running egg_info
writing Django.egg-info/PKG-INFO
writing dependency_links to Django.egg-info/dependency_links.txt
writing entry points to Django.egg-info/entry_points.txt
writing requirements to Django.egg-info/requires.txt
writing top-level names to Django.egg-info/top_level.txt
reading manifest file 'Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '*.py[co]' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file 'Django.egg-info/SOURCES.txt'
Handling wheel from get_requires_for_build_wheel
Requirement not satisfied: wheel
Exiting dependency generation pass: get_requires_for_build_wheel
+ cat /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires
+ rm -rfv '*.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-django-4.2.3-1.fc40.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 70 kB/s | 1.5 kB 00:00
fedora 80 kB/s | 22 kB 00:00
Package bash-completion-1:2.11-12.fc39.noarch is already installed.
Package make-1:4.4.1-2.fc39.x86_64 is already installed.
Package pyproject-rpm-macros-1.9.0-2.fc40.noarch is already installed.
Package python3-asgiref-3.6.0-4.fc40.noarch is already installed.
Package python3-devel-3.12.0~rc1-1.fc40.x86_64 is already installed.
Package python3-devel-3.12.0~rc1-1.fc40.x86_64 is already installed.
Package python3-aiosmtpd-1.4.4.post2-6.fc40.noarch is already installed.
Package python3-argon2-cffi-21.3.0-4.fc39.noarch is already installed.
Package python3-asgiref-3.6.0-4.fc40.noarch is already installed.
Package python3-bcrypt-4.0.1-5.fc40.x86_64 is already installed.
Package python3-cx-oracle-8.3.0-5.fc40.x86_64 is already installed.
Package python3-docutils-0.20.1-1.fc40.noarch is already installed.
Package python3-jinja2-3.1.2-5.fc39.noarch is already installed.
Package python3-mysqlclient-2.1.1-5.fc39.x86_64 is already installed.
Package python3-packaging-23.1-4.fc39.noarch is already installed.
Package python3-pillow-10.0.0-2.fc39.x86_64 is already installed.
Package python3-pip-23.2.1-1.fc40.noarch is already installed.
Package python3-psycopg3-3.1.10-1.fc39.noarch is already installed.
Package python3-enchant-3.2.2-9.fc39.noarch is already installed.
Package python3-pylibmc-1.6.3-4.fc39.x86_64 is already installed.
Package python3-pymemcache-3.5.0-8.fc39.noarch is already installed.
Package python3-pytz-2023.3-3.fc39.noarch is already installed.
Package python3-pyyaml-6.0.1-12.fc40.x86_64 is already installed.
Package python3-redis-4.5.1-3.fc39.noarch is already installed.
Package python3-selenium-3.141.0-4.fc39.noarch is already installed.
Package python3-setuptools-67.7.2-5.fc39.noarch is already installed.
Package python3-sphinx-1:7.0.1-1.fc40.noarch is already installed.
Package python3-sphinxcontrib-spelling-7.3.3-6.fc39.noarch is already installed.
Package python3-sqlparse-0.4.2-7.fc39.noarch is already installed.
Package python3-tblib-2.0.0-4.fc39.noarch is already installed.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Installing:
python3-wheel noarch 1:0.41.1-1.fc40 copr_base 148 k
Transaction Summary
================================================================================
Install 1 Package
Total size: 148 k
Installed size: 505 k
Downloading Packages:
[SKIPPED] python3-wheel-0.41.1-1.fc40.noarch.rpm: Already downloaded
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : python3-wheel-1:0.41.1-1.fc40.noarch 1/1
Running scriptlet: python3-wheel-1:0.41.1-1.fc40.noarch 1/1
Verifying : python3-wheel-1:0.41.1-1.fc40.noarch 1/1
Installed:
python3-wheel-1:0.41.1-1.fc40.noarch
Complete!
error: %changelog not in descending chronological order
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1689724800
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.vRTh48
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf Django-4.2.3
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/Django-4.2.3.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd Django-4.2.3
+ rm -rf /builddir/build/BUILD/Django-4.2.3-SPECPARTS
+ /usr/bin/mkdir -p /builddir/build/BUILD/Django-4.2.3-SPECPARTS
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/dirty-hack-remove-assert.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f
+ pushd django
~/build/BUILD/Django-4.2.3/django ~/build/BUILD/Django-4.2.3
+ for file in conf/project_template/manage.py-tpl
+ sed -i 's/\/env python/\/python3/' conf/project_template/manage.py-tpl
+ popd
~/build/BUILD/Django-4.2.3
+ sed -i 's/psycopg\[binary\]>=3\.1\.8/psycopg>=3.1.8/' tests/requirements/postgres.txt
+ sed -i '/^pywatchman\b/d' tests/requirements/py3.txt
+ sed -i '/^tzdata$/d' tests/requirements/py3.txt
+ sed -i '/^black\b/d' tests/requirements/py3.txt
+ sed -i '/^blacken-docs\b/d' docs/requirements.txt
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.LWlf1E
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ TMPDIR=/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ RPM_TOXENV=py312
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir --output /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires -r tests/requirements/py3.txt tests/requirements/postgres.txt tests/requirements/mysql.txt tests/requirements/oracle.txt docs/requirements.txt
Handling aiosmtpd from requirements file tests/requirements/py3.txt
Requirement satisfied: aiosmtpd
(installed: aiosmtpd 1.4.4.post2)
Handling asgiref >= 3.6.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: asgiref >= 3.6.0
(installed: asgiref 3.6.0)
Handling argon2-cffi >= 19.2.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: argon2-cffi >= 19.2.0
(installed: argon2-cffi 21.3.0)
Handling backports.zoneinfo; python_version < '3.9' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: backports.zoneinfo; python_version < '3.9'
Handling bcrypt from requirements file tests/requirements/py3.txt
Requirement satisfied: bcrypt
(installed: bcrypt 4.0.1)
Handling docutils from requirements file tests/requirements/py3.txt
Requirement satisfied: docutils
(installed: docutils 0.20.1)
Handling geoip2; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: geoip2; python_version < '3.12'
Handling jinja2 >= 2.11.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: jinja2 >= 2.11.0
(installed: jinja2 3.1.2)
Handling numpy; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: numpy; python_version < '3.12'
Handling Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12' from requirements file tests/requirements/py3.txt
Requirement satisfied: Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12'
(installed: Pillow 10.0.0)
Handling pylibmc; sys.platform != 'win32' from requirements file tests/requirements/py3.txt
Requirement satisfied: pylibmc; sys.platform != 'win32'
(installed: pylibmc 1.6.3)
Handling pymemcache >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: pymemcache >= 3.4.0
(installed: pymemcache 3.5.0)
Handling pytz from requirements file tests/requirements/py3.txt
Requirement satisfied: pytz
(installed: pytz 2023.3)
Handling PyYAML from requirements file tests/requirements/py3.txt
Requirement satisfied: PyYAML
(installed: PyYAML 6.0.1)
Handling redis >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: redis >= 3.4.0
(installed: redis 4.5.1)
Handling selenium >= 3.8.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: selenium >= 3.8.0
(installed: selenium 3.141.0)
Handling sqlparse >= 0.3.1 from requirements file tests/requirements/py3.txt
Requirement satisfied: sqlparse >= 0.3.1
(installed: sqlparse 0.4.2)
Handling tblib >= 1.5.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: tblib >= 1.5.0
(installed: tblib 2.0.0)
Handling colorama; sys.platform == 'win32' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: colorama; sys.platform == 'win32'
Handling psycopg>=3.1.8 from requirements file tests/requirements/postgres.txt
Requirement satisfied: psycopg>=3.1.8
(installed: psycopg 3.1.10)
Handling mysqlclient >= 1.4.3 from requirements file tests/requirements/mysql.txt
Requirement satisfied: mysqlclient >= 1.4.3
(installed: mysqlclient 2.1.1)
Handling cx_oracle >= 7.0 from requirements file tests/requirements/oracle.txt
Requirement satisfied: cx_oracle >= 7.0
(installed: cx_oracle 8.3.0)
Handling pyenchant from requirements file docs/requirements.txt
Requirement satisfied: pyenchant
(installed: pyenchant 3.2.2)
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement satisfied: Sphinx>=4.5.0
(installed: Sphinx 7.0.1)
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement satisfied: sphinxcontrib-spelling
(installed: sphinxcontrib-spelling 7.3.3)
Handling setuptools>=40.8.0 from build-system.requires
Requirement satisfied: setuptools>=40.8.0
(installed: setuptools 67.7.2)
running egg_info
writing Django.egg-info/PKG-INFO
writing dependency_links to Django.egg-info/dependency_links.txt
writing entry points to Django.egg-info/entry_points.txt
writing requirements to Django.egg-info/requires.txt
writing top-level names to Django.egg-info/top_level.txt
reading manifest file 'Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '*.py[co]' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file 'Django.egg-info/SOURCES.txt'
Handling wheel from get_requires_for_build_wheel
Requirement satisfied: wheel
(installed: wheel 0.41.1)
running dist_info
writing Django.egg-info/PKG-INFO
writing dependency_links to Django.egg-info/dependency_links.txt
writing entry points to Django.egg-info/entry_points.txt
writing requirements to Django.egg-info/requires.txt
writing top-level names to Django.egg-info/top_level.txt
reading manifest file 'Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '*.py[co]' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file 'Django.egg-info/SOURCES.txt'
creating '/builddir/build/BUILD/Django-4.2.3/Django-4.2.3.dist-info'
Handling asgiref <4,>=3.6.0 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: asgiref <4,>=3.6.0
(installed: asgiref 3.6.0)
Handling sqlparse >=0.3.1 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: sqlparse >=0.3.1
(installed: sqlparse 0.4.2)
Handling backports.zoneinfo ; python_version < "3.9" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: backports.zoneinfo ; python_version < "3.9"
Handling tzdata ; sys_platform == "win32" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: tzdata ; sys_platform == "win32"
Handling argon2-cffi >=19.1.0 ; extra == 'argon2' from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: argon2-cffi >=19.1.0 ; extra == 'argon2'
Handling bcrypt ; extra == 'bcrypt' from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: bcrypt ; extra == 'bcrypt'
+ cat /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires
+ rm -rfv Django-4.2.3.dist-info/
removed 'Django-4.2.3.dist-info/AUTHORS'
removed 'Django-4.2.3.dist-info/LICENSE.python'
removed 'Django-4.2.3.dist-info/LICENSE'
removed 'Django-4.2.3.dist-info/METADATA'
removed 'Django-4.2.3.dist-info/entry_points.txt'
removed 'Django-4.2.3.dist-info/top_level.txt'
removed directory 'Django-4.2.3.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Wrote: /builddir/build/SRPMS/python-django-4.2.3-1.fc40.buildreqs.nosrc.rpm
INFO: Going to install missing dynamic buildrequires
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Copr repository 91 kB/s | 1.5 kB 00:00
Copr repository 30 MB/s | 1.7 MB 00:00
fedora 269 kB/s | 22 kB 00:00
Package python3-asgiref-3.6.0-4.fc40.noarch is already installed.
Package bash-completion-1:2.11-12.fc39.noarch is already installed.
Package make-1:4.4.1-2.fc39.x86_64 is already installed.
Package pyproject-rpm-macros-1.9.0-2.fc40.noarch is already installed.
Package python3-asgiref-3.6.0-4.fc40.noarch is already installed.
Package python3-devel-3.12.0~rc1-1.fc40.x86_64 is already installed.
Package python3-devel-3.12.0~rc1-1.fc40.x86_64 is already installed.
Package python3-aiosmtpd-1.4.4.post2-6.fc40.noarch is already installed.
Package python3-argon2-cffi-21.3.0-4.fc39.noarch is already installed.
Package python3-asgiref-3.6.0-4.fc40.noarch is already installed.
Package python3-bcrypt-4.0.1-5.fc40.x86_64 is already installed.
Package python3-cx-oracle-8.3.0-5.fc40.x86_64 is already installed.
Package python3-docutils-0.20.1-1.fc40.noarch is already installed.
Package python3-jinja2-3.1.2-5.fc39.noarch is already installed.
Package python3-mysqlclient-2.1.1-5.fc39.x86_64 is already installed.
Package python3-packaging-23.1-4.fc39.noarch is already installed.
Package python3-pillow-10.0.0-2.fc39.x86_64 is already installed.
Package python3-pip-23.2.1-1.fc40.noarch is already installed.
Package python3-psycopg3-3.1.10-1.fc39.noarch is already installed.
Package python3-enchant-3.2.2-9.fc39.noarch is already installed.
Package python3-pylibmc-1.6.3-4.fc39.x86_64 is already installed.
Package python3-pymemcache-3.5.0-8.fc39.noarch is already installed.
Package python3-pytz-2023.3-3.fc39.noarch is already installed.
Package python3-pyyaml-6.0.1-12.fc40.x86_64 is already installed.
Package python3-redis-4.5.1-3.fc39.noarch is already installed.
Package python3-selenium-3.141.0-4.fc39.noarch is already installed.
Package python3-setuptools-67.7.2-5.fc39.noarch is already installed.
Package python3-sphinx-1:7.0.1-1.fc40.noarch is already installed.
Package python3-sphinxcontrib-spelling-7.3.3-6.fc39.noarch is already installed.
Package python3-sqlparse-0.4.2-7.fc39.noarch is already installed.
Package python3-tblib-2.0.0-4.fc39.noarch is already installed.
Package python3-wheel-1:0.41.1-1.fc40.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
error: %changelog not in descending chronological order
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1689724800
Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.5vqHV2
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ echo pyproject-rpm-macros
+ echo python3-devel
+ echo 'python3dist(pip) >= 19'
+ echo 'python3dist(packaging)'
+ '[' -f pyproject.toml ']'
+ echo '(python3dist(tomli) if python3-devel < 3.11)'
+ rm -rfv '*.dist-info/'
+ '[' -f /usr/bin/python3 ']'
+ mkdir -p /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ echo -n
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 '
+ TMPDIR=/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ RPM_TOXENV=py312
+ HOSTNAME=rpmbuild
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir --output /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires -r tests/requirements/py3.txt tests/requirements/postgres.txt tests/requirements/mysql.txt tests/requirements/oracle.txt docs/requirements.txt
Handling aiosmtpd from requirements file tests/requirements/py3.txt
Requirement satisfied: aiosmtpd
(installed: aiosmtpd 1.4.4.post2)
Handling asgiref >= 3.6.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: asgiref >= 3.6.0
(installed: asgiref 3.6.0)
Handling argon2-cffi >= 19.2.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: argon2-cffi >= 19.2.0
(installed: argon2-cffi 21.3.0)
Handling backports.zoneinfo; python_version < '3.9' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: backports.zoneinfo; python_version < '3.9'
Handling bcrypt from requirements file tests/requirements/py3.txt
Requirement satisfied: bcrypt
(installed: bcrypt 4.0.1)
Handling docutils from requirements file tests/requirements/py3.txt
Requirement satisfied: docutils
(installed: docutils 0.20.1)
Handling geoip2; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: geoip2; python_version < '3.12'
Handling jinja2 >= 2.11.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: jinja2 >= 2.11.0
(installed: jinja2 3.1.2)
Handling numpy; python_version < '3.12' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: numpy; python_version < '3.12'
Handling Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12' from requirements file tests/requirements/py3.txt
Requirement satisfied: Pillow >= 6.2.1; sys.platform != 'win32' or python_version < '3.12'
(installed: Pillow 10.0.0)
Handling pylibmc; sys.platform != 'win32' from requirements file tests/requirements/py3.txt
Requirement satisfied: pylibmc; sys.platform != 'win32'
(installed: pylibmc 1.6.3)
Handling pymemcache >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: pymemcache >= 3.4.0
(installed: pymemcache 3.5.0)
Handling pytz from requirements file tests/requirements/py3.txt
Requirement satisfied: pytz
(installed: pytz 2023.3)
Handling PyYAML from requirements file tests/requirements/py3.txt
Requirement satisfied: PyYAML
(installed: PyYAML 6.0.1)
Handling redis >= 3.4.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: redis >= 3.4.0
(installed: redis 4.5.1)
Handling selenium >= 3.8.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: selenium >= 3.8.0
(installed: selenium 3.141.0)
Handling sqlparse >= 0.3.1 from requirements file tests/requirements/py3.txt
Requirement satisfied: sqlparse >= 0.3.1
(installed: sqlparse 0.4.2)
Handling tblib >= 1.5.0 from requirements file tests/requirements/py3.txt
Requirement satisfied: tblib >= 1.5.0
(installed: tblib 2.0.0)
Handling colorama; sys.platform == 'win32' from requirements file tests/requirements/py3.txt
Ignoring alien requirement: colorama; sys.platform == 'win32'
Handling psycopg>=3.1.8 from requirements file tests/requirements/postgres.txt
Requirement satisfied: psycopg>=3.1.8
(installed: psycopg 3.1.10)
Handling mysqlclient >= 1.4.3 from requirements file tests/requirements/mysql.txt
Requirement satisfied: mysqlclient >= 1.4.3
(installed: mysqlclient 2.1.1)
Handling cx_oracle >= 7.0 from requirements file tests/requirements/oracle.txt
Requirement satisfied: cx_oracle >= 7.0
(installed: cx_oracle 8.3.0)
Handling pyenchant from requirements file docs/requirements.txt
Requirement satisfied: pyenchant
(installed: pyenchant 3.2.2)
Handling Sphinx>=4.5.0 from requirements file docs/requirements.txt
Requirement satisfied: Sphinx>=4.5.0
(installed: Sphinx 7.0.1)
Handling sphinxcontrib-spelling from requirements file docs/requirements.txt
Requirement satisfied: sphinxcontrib-spelling
(installed: sphinxcontrib-spelling 7.3.3)
Handling setuptools>=40.8.0 from build-system.requires
Requirement satisfied: setuptools>=40.8.0
(installed: setuptools 67.7.2)
running egg_info
writing Django.egg-info/PKG-INFO
writing dependency_links to Django.egg-info/dependency_links.txt
writing entry points to Django.egg-info/entry_points.txt
writing requirements to Django.egg-info/requires.txt
writing top-level names to Django.egg-info/top_level.txt
reading manifest file 'Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '*.py[co]' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file 'Django.egg-info/SOURCES.txt'
Handling wheel from get_requires_for_build_wheel
Requirement satisfied: wheel
(installed: wheel 0.41.1)
running dist_info
writing Django.egg-info/PKG-INFO
writing dependency_links to Django.egg-info/dependency_links.txt
writing entry points to Django.egg-info/entry_points.txt
writing requirements to Django.egg-info/requires.txt
writing top-level names to Django.egg-info/top_level.txt
reading manifest file 'Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '*.py[co]' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file 'Django.egg-info/SOURCES.txt'
creating '/builddir/build/BUILD/Django-4.2.3/Django-4.2.3.dist-info'
Handling asgiref <4,>=3.6.0 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: asgiref <4,>=3.6.0
(installed: asgiref 3.6.0)
Handling sqlparse >=0.3.1 from hook generated metadata: Requires-Dist (Django)
Requirement satisfied: sqlparse >=0.3.1
(installed: sqlparse 0.4.2)
Handling backports.zoneinfo ; python_version < "3.9" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: backports.zoneinfo ; python_version < "3.9"
Handling tzdata ; sys_platform == "win32" from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: tzdata ; sys_platform == "win32"
Handling argon2-cffi >=19.1.0 ; extra == 'argon2' from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: argon2-cffi >=19.1.0 ; extra == 'argon2'
Handling bcrypt ; extra == 'bcrypt' from hook generated metadata: Requires-Dist (Django)
Ignoring alien requirement: bcrypt ; extra == 'bcrypt'
+ cat /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-buildrequires
+ rm -rfv Django-4.2.3.dist-info/
removed 'Django-4.2.3.dist-info/AUTHORS'
removed 'Django-4.2.3.dist-info/LICENSE.python'
removed 'Django-4.2.3.dist-info/LICENSE'
removed 'Django-4.2.3.dist-info/METADATA'
removed 'Django-4.2.3.dist-info/top_level.txt'
removed 'Django-4.2.3.dist-info/entry_points.txt'
removed directory 'Django-4.2.3.dist-info/'
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.Iw5Y5q
+ umask 022
+ cd /builddir/build/BUILD
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd Django-4.2.3
+ mkdir -p /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ TMPDIR=/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir
Processing /builddir/build/BUILD/Django-4.2.3
Preparing metadata (pyproject.toml): started
Running command Preparing metadata (pyproject.toml)
running dist_info
creating /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info
writing /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/PKG-INFO
writing dependency_links to /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/dependency_links.txt
writing entry points to /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/entry_points.txt
writing requirements to /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/requires.txt
writing top-level names to /builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/top_level.txt
writing manifest file '/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/SOURCES.txt'
reading manifest file '/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file '/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django.egg-info/SOURCES.txt'
creating '/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-modern-metadata-6hhd3i_6/Django-4.2.3.dist-info'
Preparing metadata (pyproject.toml): finished with status 'done'
Building wheels for collected packages: Django
Building wheel for Django (pyproject.toml): started
Running command Building wheel for Django (pyproject.toml)
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/django
copying django/shortcuts.py -> build/lib/django
copying django/__main__.py -> build/lib/django
copying django/__init__.py -> build/lib/django
creating build/lib/django/views
copying django/views/static.py -> build/lib/django/views
copying django/views/i18n.py -> build/lib/django/views
copying django/views/defaults.py -> build/lib/django/views
copying django/views/debug.py -> build/lib/django/views
copying django/views/csrf.py -> build/lib/django/views
copying django/views/__init__.py -> build/lib/django/views
creating build/lib/django/utils
copying django/utils/xmlutils.py -> build/lib/django/utils
copying django/utils/version.py -> build/lib/django/utils
copying django/utils/tree.py -> build/lib/django/utils
copying django/utils/topological_sort.py -> build/lib/django/utils
copying django/utils/timezone.py -> build/lib/django/utils
copying django/utils/timesince.py -> build/lib/django/utils
copying django/utils/text.py -> build/lib/django/utils
copying django/utils/termcolors.py -> build/lib/django/utils
copying django/utils/safestring.py -> build/lib/django/utils
copying django/utils/regex_helper.py -> build/lib/django/utils
copying django/utils/numberformat.py -> build/lib/django/utils
copying django/utils/module_loading.py -> build/lib/django/utils
copying django/utils/lorem_ipsum.py -> build/lib/django/utils
copying django/utils/log.py -> build/lib/django/utils
copying django/utils/jslex.py -> build/lib/django/utils
copying django/utils/itercompat.py -> build/lib/django/utils
copying django/utils/ipv6.py -> build/lib/django/utils
copying django/utils/inspect.py -> build/lib/django/utils
copying django/utils/http.py -> build/lib/django/utils
copying django/utils/html.py -> build/lib/django/utils
copying django/utils/hashable.py -> build/lib/django/utils
copying django/utils/functional.py -> build/lib/django/utils
copying django/utils/formats.py -> build/lib/django/utils
copying django/utils/feedgenerator.py -> build/lib/django/utils
copying django/utils/encoding.py -> build/lib/django/utils
copying django/utils/duration.py -> build/lib/django/utils
copying django/utils/deprecation.py -> build/lib/django/utils
copying django/utils/decorators.py -> build/lib/django/utils
copying django/utils/deconstruct.py -> build/lib/django/utils
copying django/utils/datetime_safe.py -> build/lib/django/utils
copying django/utils/dates.py -> build/lib/django/utils
copying django/utils/dateparse.py -> build/lib/django/utils
copying django/utils/dateformat.py -> build/lib/django/utils
copying django/utils/datastructures.py -> build/lib/django/utils
copying django/utils/crypto.py -> build/lib/django/utils
copying django/utils/connection.py -> build/lib/django/utils
copying django/utils/cache.py -> build/lib/django/utils
copying django/utils/baseconv.py -> build/lib/django/utils
copying django/utils/autoreload.py -> build/lib/django/utils
copying django/utils/asyncio.py -> build/lib/django/utils
copying django/utils/archive.py -> build/lib/django/utils
copying django/utils/_os.py -> build/lib/django/utils
copying django/utils/__init__.py -> build/lib/django/utils
creating build/lib/django/urls
copying django/urls/utils.py -> build/lib/django/urls
copying django/urls/resolvers.py -> build/lib/django/urls
copying django/urls/exceptions.py -> build/lib/django/urls
copying django/urls/converters.py -> build/lib/django/urls
copying django/urls/conf.py -> build/lib/django/urls
copying django/urls/base.py -> build/lib/django/urls
copying django/urls/__init__.py -> build/lib/django/urls
creating build/lib/django/test
copying django/test/utils.py -> build/lib/django/test
copying django/test/testcases.py -> build/lib/django/test
copying django/test/signals.py -> build/lib/django/test
copying django/test/selenium.py -> build/lib/django/test
copying django/test/runner.py -> build/lib/django/test
copying django/test/html.py -> build/lib/django/test
copying django/test/client.py -> build/lib/django/test
copying django/test/__init__.py -> build/lib/django/test
creating build/lib/django/templatetags
copying django/templatetags/tz.py -> build/lib/django/templatetags
copying django/templatetags/static.py -> build/lib/django/templatetags
copying django/templatetags/l10n.py -> build/lib/django/templatetags
copying django/templatetags/i18n.py -> build/lib/django/templatetags
copying django/templatetags/cache.py -> build/lib/django/templatetags
copying django/templatetags/__init__.py -> build/lib/django/templatetags
creating build/lib/django/template
copying django/template/utils.py -> build/lib/django/template
copying django/template/smartif.py -> build/lib/django/template
copying django/template/response.py -> build/lib/django/template
copying django/template/loader_tags.py -> build/lib/django/template
copying django/template/loader.py -> build/lib/django/template
copying django/template/library.py -> build/lib/django/template
copying django/template/exceptions.py -> build/lib/django/template
copying django/template/engine.py -> build/lib/django/template
copying django/template/defaulttags.py -> build/lib/django/template
copying django/template/defaultfilters.py -> build/lib/django/template
copying django/template/context_processors.py -> build/lib/django/template
copying django/template/context.py -> build/lib/django/template
copying django/template/base.py -> build/lib/django/template
copying django/template/autoreload.py -> build/lib/django/template
copying django/template/__init__.py -> build/lib/django/template
creating build/lib/django/middleware
copying django/middleware/security.py -> build/lib/django/middleware
copying django/middleware/locale.py -> build/lib/django/middleware
copying django/middleware/http.py -> build/lib/django/middleware
copying django/middleware/gzip.py -> build/lib/django/middleware
copying django/middleware/csrf.py -> build/lib/django/middleware
copying django/middleware/common.py -> build/lib/django/middleware
copying django/middleware/clickjacking.py -> build/lib/django/middleware
copying django/middleware/cache.py -> build/lib/django/middleware
copying django/middleware/__init__.py -> build/lib/django/middleware
creating build/lib/django/http
copying django/http/response.py -> build/lib/django/http
copying django/http/request.py -> build/lib/django/http
copying django/http/multipartparser.py -> build/lib/django/http
copying django/http/cookie.py -> build/lib/django/http
copying django/http/__init__.py -> build/lib/django/http
creating build/lib/django/forms
copying django/forms/widgets.py -> build/lib/django/forms
copying django/forms/utils.py -> build/lib/django/forms
copying django/forms/renderers.py -> build/lib/django/forms
copying django/forms/models.py -> build/lib/django/forms
copying django/forms/formsets.py -> build/lib/django/forms
copying django/forms/forms.py -> build/lib/django/forms
copying django/forms/fields.py -> build/lib/django/forms
copying django/forms/boundfield.py -> build/lib/django/forms
copying django/forms/__init__.py -> build/lib/django/forms
creating build/lib/django/dispatch
copying django/dispatch/dispatcher.py -> build/lib/django/dispatch
copying django/dispatch/__init__.py -> build/lib/django/dispatch
creating build/lib/django/db
copying django/db/utils.py -> build/lib/django/db
copying django/db/transaction.py -> build/lib/django/db
copying django/db/__init__.py -> build/lib/django/db
creating build/lib/django/core
copying django/core/wsgi.py -> build/lib/django/core
copying django/core/validators.py -> build/lib/django/core
copying django/core/signing.py -> build/lib/django/core
copying django/core/signals.py -> build/lib/django/core
copying django/core/paginator.py -> build/lib/django/core
copying django/core/exceptions.py -> build/lib/django/core
copying django/core/asgi.py -> build/lib/django/core
copying django/core/__init__.py -> build/lib/django/core
creating build/lib/django/contrib
copying django/contrib/__init__.py -> build/lib/django/contrib
creating build/lib/django/conf
copying django/conf/global_settings.py -> build/lib/django/conf
copying django/conf/__init__.py -> build/lib/django/conf
creating build/lib/django/apps
copying django/apps/registry.py -> build/lib/django/apps
copying django/apps/config.py -> build/lib/django/apps
copying django/apps/__init__.py -> build/lib/django/apps
creating build/lib/django/views/generic
copying django/views/generic/list.py -> build/lib/django/views/generic
copying django/views/generic/edit.py -> build/lib/django/views/generic
copying django/views/generic/detail.py -> build/lib/django/views/generic
copying django/views/generic/dates.py -> build/lib/django/views/generic
copying django/views/generic/base.py -> build/lib/django/views/generic
copying django/views/generic/__init__.py -> build/lib/django/views/generic
creating build/lib/django/views/decorators
copying django/views/decorators/vary.py -> build/lib/django/views/decorators
copying django/views/decorators/http.py -> build/lib/django/views/decorators
copying django/views/decorators/gzip.py -> build/lib/django/views/decorators
copying django/views/decorators/debug.py -> build/lib/django/views/decorators
copying django/views/decorators/csrf.py -> build/lib/django/views/decorators
copying django/views/decorators/common.py -> build/lib/django/views/decorators
copying django/views/decorators/clickjacking.py -> build/lib/django/views/decorators
copying django/views/decorators/cache.py -> build/lib/django/views/decorators
copying django/views/decorators/__init__.py -> build/lib/django/views/decorators
creating build/lib/django/utils/translation
copying django/utils/translation/trans_real.py -> build/lib/django/utils/translation
copying django/utils/translation/trans_null.py -> build/lib/django/utils/translation
copying django/utils/translation/template.py -> build/lib/django/utils/translation
copying django/utils/translation/reloader.py -> build/lib/django/utils/translation
copying django/utils/translation/__init__.py -> build/lib/django/utils/translation
creating build/lib/django/template/loaders
copying django/template/loaders/locmem.py -> build/lib/django/template/loaders
copying django/template/loaders/filesystem.py -> build/lib/django/template/loaders
copying django/template/loaders/cached.py -> build/lib/django/template/loaders
copying django/template/loaders/base.py -> build/lib/django/template/loaders
copying django/template/loaders/app_directories.py -> build/lib/django/template/loaders
copying django/template/loaders/__init__.py -> build/lib/django/template/loaders
creating build/lib/django/template/backends
copying django/template/backends/utils.py -> build/lib/django/template/backends
copying django/template/backends/jinja2.py -> build/lib/django/template/backends
copying django/template/backends/dummy.py -> build/lib/django/template/backends
copying django/template/backends/django.py -> build/lib/django/template/backends
copying django/template/backends/base.py -> build/lib/django/template/backends
copying django/template/backends/__init__.py -> build/lib/django/template/backends
creating build/lib/django/db/models
copying django/db/models/utils.py -> build/lib/django/db/models
copying django/db/models/signals.py -> build/lib/django/db/models
copying django/db/models/query_utils.py -> build/lib/django/db/models
copying django/db/models/query.py -> build/lib/django/db/models
copying django/db/models/options.py -> build/lib/django/db/models
copying django/db/models/manager.py -> build/lib/django/db/models
copying django/db/models/lookups.py -> build/lib/django/db/models
copying django/db/models/indexes.py -> build/lib/django/db/models
copying django/db/models/expressions.py -> build/lib/django/db/models
copying django/db/models/enums.py -> build/lib/django/db/models
copying django/db/models/deletion.py -> build/lib/django/db/models
copying django/db/models/constraints.py -> build/lib/django/db/models
copying django/db/models/constants.py -> build/lib/django/db/models
copying django/db/models/base.py -> build/lib/django/db/models
copying django/db/models/aggregates.py -> build/lib/django/db/models
copying django/db/models/__init__.py -> build/lib/django/db/models
creating build/lib/django/db/migrations
copying django/db/migrations/writer.py -> build/lib/django/db/migrations
copying django/db/migrations/utils.py -> build/lib/django/db/migrations
copying django/db/migrations/state.py -> build/lib/django/db/migrations
copying django/db/migrations/serializer.py -> build/lib/django/db/migrations
copying django/db/migrations/recorder.py -> build/lib/django/db/migrations
copying django/db/migrations/questioner.py -> build/lib/django/db/migrations
copying django/db/migrations/optimizer.py -> build/lib/django/db/migrations
copying django/db/migrations/migration.py -> build/lib/django/db/migrations
copying django/db/migrations/loader.py -> build/lib/django/db/migrations
copying django/db/migrations/graph.py -> build/lib/django/db/migrations
copying django/db/migrations/executor.py -> build/lib/django/db/migrations
copying django/db/migrations/exceptions.py -> build/lib/django/db/migrations
copying django/db/migrations/autodetector.py -> build/lib/django/db/migrations
copying django/db/migrations/__init__.py -> build/lib/django/db/migrations
creating build/lib/django/db/backends
copying django/db/backends/utils.py -> build/lib/django/db/backends
copying django/db/backends/signals.py -> build/lib/django/db/backends
copying django/db/backends/ddl_references.py -> build/lib/django/db/backends
copying django/db/backends/__init__.py -> build/lib/django/db/backends
creating build/lib/django/db/models/sql
copying django/db/models/sql/where.py -> build/lib/django/db/models/sql
copying django/db/models/sql/subqueries.py -> build/lib/django/db/models/sql
copying django/db/models/sql/query.py -> build/lib/django/db/models/sql
copying django/db/models/sql/datastructures.py -> build/lib/django/db/models/sql
copying django/db/models/sql/constants.py -> build/lib/django/db/models/sql
copying django/db/models/sql/compiler.py -> build/lib/django/db/models/sql
copying django/db/models/sql/__init__.py -> build/lib/django/db/models/sql
creating build/lib/django/db/models/functions
copying django/db/models/functions/window.py -> build/lib/django/db/models/functions
copying django/db/models/functions/text.py -> build/lib/django/db/models/functions
copying django/db/models/functions/mixins.py -> build/lib/django/db/models/functions
copying django/db/models/functions/math.py -> build/lib/django/db/models/functions
copying django/db/models/functions/datetime.py -> build/lib/django/db/models/functions
copying django/db/models/functions/comparison.py -> build/lib/django/db/models/functions
copying django/db/models/functions/__init__.py -> build/lib/django/db/models/functions
creating build/lib/django/db/models/fields
copying django/db/models/fields/reverse_related.py -> build/lib/django/db/models/fields
copying django/db/models/fields/related_lookups.py -> build/lib/django/db/models/fields
copying django/db/models/fields/related_descriptors.py -> build/lib/django/db/models/fields
copying django/db/models/fields/related.py -> build/lib/django/db/models/fields
copying django/db/models/fields/proxy.py -> build/lib/django/db/models/fields
copying django/db/models/fields/mixins.py -> build/lib/django/db/models/fields
copying django/db/models/fields/json.py -> build/lib/django/db/models/fields
copying django/db/models/fields/files.py -> build/lib/django/db/models/fields
copying django/db/models/fields/__init__.py -> build/lib/django/db/models/fields
creating build/lib/django/db/migrations/operations
copying django/db/migrations/operations/special.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/models.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/fields.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/base.py -> build/lib/django/db/migrations/operations
copying django/db/migrations/operations/__init__.py -> build/lib/django/db/migrations/operations
creating build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/schema.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/operations.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/introspection.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/features.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/creation.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/client.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/base.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/_functions.py -> build/lib/django/db/backends/sqlite3
copying django/db/backends/sqlite3/__init__.py -> build/lib/django/db/backends/sqlite3
creating build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/schema.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/psycopg_any.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/operations.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/introspection.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/features.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/creation.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/client.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/base.py -> build/lib/django/db/backends/postgresql
copying django/db/backends/postgresql/__init__.py -> build/lib/django/db/backends/postgresql
creating build/lib/django/db/backends/oracle
copying django/db/backends/oracle/validation.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/utils.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/schema.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/operations.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/introspection.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/functions.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/features.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/creation.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/client.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/base.py -> build/lib/django/db/backends/oracle
copying django/db/backends/oracle/__init__.py -> build/lib/django/db/backends/oracle
creating build/lib/django/db/backends/mysql
copying django/db/backends/mysql/validation.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/schema.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/operations.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/introspection.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/features.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/creation.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/compiler.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/client.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/base.py -> build/lib/django/db/backends/mysql
copying django/db/backends/mysql/__init__.py -> build/lib/django/db/backends/mysql
creating build/lib/django/db/backends/dummy
copying django/db/backends/dummy/features.py -> build/lib/django/db/backends/dummy
copying django/db/backends/dummy/base.py -> build/lib/django/db/backends/dummy
copying django/db/backends/dummy/__init__.py -> build/lib/django/db/backends/dummy
creating build/lib/django/db/backends/base
copying django/db/backends/base/validation.py -> build/lib/django/db/backends/base
copying django/db/backends/base/schema.py -> build/lib/django/db/backends/base
copying django/db/backends/base/operations.py -> build/lib/django/db/backends/base
copying django/db/backends/base/introspection.py -> build/lib/django/db/backends/base
copying django/db/backends/base/features.py -> build/lib/django/db/backends/base
copying django/db/backends/base/creation.py -> build/lib/django/db/backends/base
copying django/db/backends/base/client.py -> build/lib/django/db/backends/base
copying django/db/backends/base/base.py -> build/lib/django/db/backends/base
copying django/db/backends/base/__init__.py -> build/lib/django/db/backends/base
creating build/lib/django/core/servers
copying django/core/servers/basehttp.py -> build/lib/django/core/servers
copying django/core/servers/__init__.py -> build/lib/django/core/servers
creating build/lib/django/core/serializers
copying django/core/serializers/xml_serializer.py -> build/lib/django/core/serializers
copying django/core/serializers/pyyaml.py -> build/lib/django/core/serializers
copying django/core/serializers/python.py -> build/lib/django/core/serializers
copying django/core/serializers/jsonl.py -> build/lib/django/core/serializers
copying django/core/serializers/json.py -> build/lib/django/core/serializers
copying django/core/serializers/base.py -> build/lib/django/core/serializers
copying django/core/serializers/__init__.py -> build/lib/django/core/serializers
creating build/lib/django/core/management
copying django/core/management/utils.py -> build/lib/django/core/management
copying django/core/management/templates.py -> build/lib/django/core/management
copying django/core/management/sql.py -> build/lib/django/core/management
copying django/core/management/color.py -> build/lib/django/core/management
copying django/core/management/base.py -> build/lib/django/core/management
copying django/core/management/__init__.py -> build/lib/django/core/management
creating build/lib/django/core/mail
copying django/core/mail/utils.py -> build/lib/django/core/mail
copying django/core/mail/message.py -> build/lib/django/core/mail
copying django/core/mail/__init__.py -> build/lib/django/core/mail
creating build/lib/django/core/handlers
copying django/core/handlers/wsgi.py -> build/lib/django/core/handlers
copying django/core/handlers/exception.py -> build/lib/django/core/handlers
copying django/core/handlers/base.py -> build/lib/django/core/handlers
copying django/core/handlers/asgi.py -> build/lib/django/core/handlers
copying django/core/handlers/__init__.py -> build/lib/django/core/handlers
creating build/lib/django/core/files
copying django/core/files/utils.py -> build/lib/django/core/files
copying django/core/files/uploadhandler.py -> build/lib/django/core/files
copying django/core/files/uploadedfile.py -> build/lib/django/core/files
copying django/core/files/temp.py -> build/lib/django/core/files
copying django/core/files/move.py -> build/lib/django/core/files
copying django/core/files/locks.py -> build/lib/django/core/files
copying django/core/files/images.py -> build/lib/django/core/files
copying django/core/files/base.py -> build/lib/django/core/files
copying django/core/files/__init__.py -> build/lib/django/core/files
creating build/lib/django/core/checks
copying django/core/checks/urls.py -> build/lib/django/core/checks
copying django/core/checks/translation.py -> build/lib/django/core/checks
copying django/core/checks/templates.py -> build/lib/django/core/checks
copying django/core/checks/registry.py -> build/lib/django/core/checks
copying django/core/checks/model_checks.py -> build/lib/django/core/checks
copying django/core/checks/messages.py -> build/lib/django/core/checks
copying django/core/checks/files.py -> build/lib/django/core/checks
copying django/core/checks/database.py -> build/lib/django/core/checks
copying django/core/checks/caches.py -> build/lib/django/core/checks
copying django/core/checks/async_checks.py -> build/lib/django/core/checks
copying django/core/checks/__init__.py -> build/lib/django/core/checks
creating build/lib/django/core/cache
copying django/core/cache/utils.py -> build/lib/django/core/cache
copying django/core/cache/__init__.py -> build/lib/django/core/cache
creating build/lib/django/core/management/commands
copying django/core/management/commands/testserver.py -> build/lib/django/core/management/commands
copying django/core/management/commands/test.py -> build/lib/django/core/management/commands
copying django/core/management/commands/startproject.py -> build/lib/django/core/management/commands
copying django/core/management/commands/startapp.py -> build/lib/django/core/management/commands
copying django/core/management/commands/squashmigrations.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sqlsequencereset.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sqlmigrate.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sqlflush.py -> build/lib/django/core/management/commands
copying django/core/management/commands/showmigrations.py -> build/lib/django/core/management/commands
copying django/core/management/commands/shell.py -> build/lib/django/core/management/commands
copying django/core/management/commands/sendtestemail.py -> build/lib/django/core/management/commands
copying django/core/management/commands/runserver.py -> build/lib/django/core/management/commands
copying django/core/management/commands/optimizemigration.py -> build/lib/django/core/management/commands
copying django/core/management/commands/migrate.py -> build/lib/django/core/management/commands
copying django/core/management/commands/makemigrations.py -> build/lib/django/core/management/commands
copying django/core/management/commands/makemessages.py -> build/lib/django/core/management/commands
copying django/core/management/commands/loaddata.py -> build/lib/django/core/management/commands
copying django/core/management/commands/inspectdb.py -> build/lib/django/core/management/commands
copying django/core/management/commands/flush.py -> build/lib/django/core/management/commands
copying django/core/management/commands/dumpdata.py -> build/lib/django/core/management/commands
copying django/core/management/commands/diffsettings.py -> build/lib/django/core/management/commands
copying django/core/management/commands/dbshell.py -> build/lib/django/core/management/commands
copying django/core/management/commands/createcachetable.py -> build/lib/django/core/management/commands
copying django/core/management/commands/compilemessages.py -> build/lib/django/core/management/commands
copying django/core/management/commands/check.py -> build/lib/django/core/management/commands
copying django/core/management/commands/__init__.py -> build/lib/django/core/management/commands
creating build/lib/django/core/mail/backends
copying django/core/mail/backends/smtp.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/locmem.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/filebased.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/dummy.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/console.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/base.py -> build/lib/django/core/mail/backends
copying django/core/mail/backends/__init__.py -> build/lib/django/core/mail/backends
creating build/lib/django/core/files/storage
copying django/core/files/storage/mixins.py -> build/lib/django/core/files/storage
copying django/core/files/storage/memory.py -> build/lib/django/core/files/storage
copying django/core/files/storage/handler.py -> build/lib/django/core/files/storage
copying django/core/files/storage/filesystem.py -> build/lib/django/core/files/storage
copying django/core/files/storage/base.py -> build/lib/django/core/files/storage
copying django/core/files/storage/__init__.py -> build/lib/django/core/files/storage
creating build/lib/django/core/checks/security
copying django/core/checks/security/sessions.py -> build/lib/django/core/checks/security
copying django/core/checks/security/csrf.py -> build/lib/django/core/checks/security
copying django/core/checks/security/base.py -> build/lib/django/core/checks/security
copying django/core/checks/security/__init__.py -> build/lib/django/core/checks/security
creating build/lib/django/core/checks/compatibility
copying django/core/checks/compatibility/django_4_0.py -> build/lib/django/core/checks/compatibility
copying django/core/checks/compatibility/__init__.py -> build/lib/django/core/checks/compatibility
creating build/lib/django/core/cache/backends
copying django/core/cache/backends/redis.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/memcached.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/locmem.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/filebased.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/dummy.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/db.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/base.py -> build/lib/django/core/cache/backends
copying django/core/cache/backends/__init__.py -> build/lib/django/core/cache/backends
creating build/lib/django/contrib/syndication
copying django/contrib/syndication/views.py -> build/lib/django/contrib/syndication
copying django/contrib/syndication/apps.py -> build/lib/django/contrib/syndication
copying django/contrib/syndication/__init__.py -> build/lib/django/contrib/syndication
creating build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/views.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/utils.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/urls.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/testing.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/storage.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/handlers.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/finders.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/checks.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/apps.py -> build/lib/django/contrib/staticfiles
copying django/contrib/staticfiles/__init__.py -> build/lib/django/contrib/staticfiles
creating build/lib/django/contrib/sites
copying django/contrib/sites/shortcuts.py -> build/lib/django/contrib/sites
copying django/contrib/sites/requests.py -> build/lib/django/contrib/sites
copying django/contrib/sites/models.py -> build/lib/django/contrib/sites
copying django/contrib/sites/middleware.py -> build/lib/django/contrib/sites
copying django/contrib/sites/managers.py -> build/lib/django/contrib/sites
copying django/contrib/sites/management.py -> build/lib/django/contrib/sites
copying django/contrib/sites/checks.py -> build/lib/django/contrib/sites
copying django/contrib/sites/apps.py -> build/lib/django/contrib/sites
copying django/contrib/sites/admin.py -> build/lib/django/contrib/sites
copying django/contrib/sites/__init__.py -> build/lib/django/contrib/sites
creating build/lib/django/contrib/sitemaps
copying django/contrib/sitemaps/views.py -> build/lib/django/contrib/sitemaps
copying django/contrib/sitemaps/apps.py -> build/lib/django/contrib/sitemaps
copying django/contrib/sitemaps/__init__.py -> build/lib/django/contrib/sitemaps
creating build/lib/django/contrib/sessions
copying django/contrib/sessions/serializers.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/models.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/middleware.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/exceptions.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/base_session.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/apps.py -> build/lib/django/contrib/sessions
copying django/contrib/sessions/__init__.py -> build/lib/django/contrib/sessions
creating build/lib/django/contrib/redirects
copying django/contrib/redirects/models.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/middleware.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/apps.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/admin.py -> build/lib/django/contrib/redirects
copying django/contrib/redirects/__init__.py -> build/lib/django/contrib/redirects
creating build/lib/django/contrib/postgres
copying django/contrib/postgres/validators.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/utils.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/signals.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/serializers.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/search.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/operations.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/lookups.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/indexes.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/functions.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/expressions.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/constraints.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/apps.py -> build/lib/django/contrib/postgres
copying django/contrib/postgres/__init__.py -> build/lib/django/contrib/postgres
creating build/lib/django/contrib/messages
copying django/contrib/messages/views.py -> build/lib/django/contrib/messages
copying django/contrib/messages/utils.py -> build/lib/django/contrib/messages
copying django/contrib/messages/middleware.py -> build/lib/django/contrib/messages
copying django/contrib/messages/context_processors.py -> build/lib/django/contrib/messages
copying django/contrib/messages/constants.py -> build/lib/django/contrib/messages
copying django/contrib/messages/apps.py -> build/lib/django/contrib/messages
copying django/contrib/messages/api.py -> build/lib/django/contrib/messages
copying django/contrib/messages/__init__.py -> build/lib/django/contrib/messages
creating build/lib/django/contrib/humanize
copying django/contrib/humanize/apps.py -> build/lib/django/contrib/humanize
copying django/contrib/humanize/__init__.py -> build/lib/django/contrib/humanize
creating build/lib/django/contrib/gis
copying django/contrib/gis/views.py -> build/lib/django/contrib/gis
copying django/contrib/gis/shortcuts.py -> build/lib/django/contrib/gis
copying django/contrib/gis/ptr.py -> build/lib/django/contrib/gis
copying django/contrib/gis/measure.py -> build/lib/django/contrib/gis
copying django/contrib/gis/geometry.py -> build/lib/django/contrib/gis
copying django/contrib/gis/feeds.py -> build/lib/django/contrib/gis
copying django/contrib/gis/apps.py -> build/lib/django/contrib/gis
copying django/contrib/gis/__init__.py -> build/lib/django/contrib/gis
creating build/lib/django/contrib/flatpages
copying django/contrib/flatpages/views.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/urls.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/sitemaps.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/models.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/middleware.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/forms.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/apps.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/admin.py -> build/lib/django/contrib/flatpages
copying django/contrib/flatpages/__init__.py -> build/lib/django/contrib/flatpages
creating build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/views.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/models.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/forms.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/fields.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/checks.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/apps.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/admin.py -> build/lib/django/contrib/contenttypes
copying django/contrib/contenttypes/__init__.py -> build/lib/django/contrib/contenttypes
creating build/lib/django/contrib/auth
copying django/contrib/auth/views.py -> build/lib/django/contrib/auth
copying django/contrib/auth/validators.py -> build/lib/django/contrib/auth
copying django/contrib/auth/urls.py -> build/lib/django/contrib/auth
copying django/contrib/auth/tokens.py -> build/lib/django/contrib/auth
copying django/contrib/auth/signals.py -> build/lib/django/contrib/auth
copying django/contrib/auth/password_validation.py -> build/lib/django/contrib/auth
copying django/contrib/auth/models.py -> build/lib/django/contrib/auth
copying django/contrib/auth/mixins.py -> build/lib/django/contrib/auth
copying django/contrib/auth/middleware.py -> build/lib/django/contrib/auth
copying django/contrib/auth/hashers.py -> build/lib/django/contrib/auth
copying django/contrib/auth/forms.py -> build/lib/django/contrib/auth
copying django/contrib/auth/decorators.py -> build/lib/django/contrib/auth
copying django/contrib/auth/context_processors.py -> build/lib/django/contrib/auth
copying django/contrib/auth/checks.py -> build/lib/django/contrib/auth
copying django/contrib/auth/base_user.py -> build/lib/django/contrib/auth
copying django/contrib/auth/backends.py -> build/lib/django/contrib/auth
copying django/contrib/auth/apps.py -> build/lib/django/contrib/auth
copying django/contrib/auth/admin.py -> build/lib/django/contrib/auth
copying django/contrib/auth/__init__.py -> build/lib/django/contrib/auth
creating build/lib/django/contrib/admindocs
copying django/contrib/admindocs/views.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/utils.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/urls.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/middleware.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/apps.py -> build/lib/django/contrib/admindocs
copying django/contrib/admindocs/__init__.py -> build/lib/django/contrib/admindocs
creating build/lib/django/contrib/admin
copying django/contrib/admin/widgets.py -> build/lib/django/contrib/admin
copying django/contrib/admin/utils.py -> build/lib/django/contrib/admin
copying django/contrib/admin/tests.py -> build/lib/django/contrib/admin
copying django/contrib/admin/sites.py -> build/lib/django/contrib/admin
copying django/contrib/admin/options.py -> build/lib/django/contrib/admin
copying django/contrib/admin/models.py -> build/lib/django/contrib/admin
copying django/contrib/admin/helpers.py -> build/lib/django/contrib/admin
copying django/contrib/admin/forms.py -> build/lib/django/contrib/admin
copying django/contrib/admin/filters.py -> build/lib/django/contrib/admin
copying django/contrib/admin/exceptions.py -> build/lib/django/contrib/admin
copying django/contrib/admin/decorators.py -> build/lib/django/contrib/admin
copying django/contrib/admin/checks.py -> build/lib/django/contrib/admin
copying django/contrib/admin/apps.py -> build/lib/django/contrib/admin
copying django/contrib/admin/actions.py -> build/lib/django/contrib/admin
copying django/contrib/admin/__init__.py -> build/lib/django/contrib/admin
creating build/lib/django/contrib/staticfiles/management
copying django/contrib/staticfiles/management/__init__.py -> build/lib/django/contrib/staticfiles/management
creating build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/runserver.py -> build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/findstatic.py -> build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/collectstatic.py -> build/lib/django/contrib/staticfiles/management/commands
copying django/contrib/staticfiles/management/commands/__init__.py -> build/lib/django/contrib/staticfiles/management/commands
creating build/lib/django/contrib/sites/migrations
copying django/contrib/sites/migrations/__init__.py -> build/lib/django/contrib/sites/migrations
copying django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/lib/django/contrib/sites/migrations
copying django/contrib/sites/migrations/0001_initial.py -> build/lib/django/contrib/sites/migrations
creating build/lib/django/contrib/sitemaps/management
copying django/contrib/sitemaps/management/__init__.py -> build/lib/django/contrib/sitemaps/management
creating build/lib/django/contrib/sitemaps/management/commands
copying django/contrib/sitemaps/management/commands/ping_google.py -> build/lib/django/contrib/sitemaps/management/commands
copying django/contrib/sitemaps/management/commands/__init__.py -> build/lib/django/contrib/sitemaps/management/commands
creating build/lib/django/contrib/sessions/migrations
copying django/contrib/sessions/migrations/__init__.py -> build/lib/django/contrib/sessions/migrations
copying django/contrib/sessions/migrations/0001_initial.py -> build/lib/django/contrib/sessions/migrations
creating build/lib/django/contrib/sessions/management
copying django/contrib/sessions/management/__init__.py -> build/lib/django/contrib/sessions/management
creating build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/signed_cookies.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/file.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/db.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/cached_db.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/cache.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/base.py -> build/lib/django/contrib/sessions/backends
copying django/contrib/sessions/backends/__init__.py -> build/lib/django/contrib/sessions/backends
creating build/lib/django/contrib/sessions/management/commands
copying django/contrib/sessions/management/commands/clearsessions.py -> build/lib/django/contrib/sessions/management/commands
copying django/contrib/sessions/management/commands/__init__.py -> build/lib/django/contrib/sessions/management/commands
creating build/lib/django/contrib/redirects/migrations
copying django/contrib/redirects/migrations/__init__.py -> build/lib/django/contrib/redirects/migrations
copying django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/lib/django/contrib/redirects/migrations
copying django/contrib/redirects/migrations/0001_initial.py -> build/lib/django/contrib/redirects/migrations
creating build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/ranges.py -> build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/hstore.py -> build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/array.py -> build/lib/django/contrib/postgres/forms
copying django/contrib/postgres/forms/__init__.py -> build/lib/django/contrib/postgres/forms
creating build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/utils.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/ranges.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/jsonb.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/hstore.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/citext.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/array.py -> build/lib/django/contrib/postgres/fields
copying django/contrib/postgres/fields/__init__.py -> build/lib/django/contrib/postgres/fields
creating build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/statistics.py -> build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/mixins.py -> build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/general.py -> build/lib/django/contrib/postgres/aggregates
copying django/contrib/postgres/aggregates/__init__.py -> build/lib/django/contrib/postgres/aggregates
creating build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/session.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/fallback.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/cookie.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/base.py -> build/lib/django/contrib/messages/storage
copying django/contrib/messages/storage/__init__.py -> build/lib/django/contrib/messages/storage
creating build/lib/django/contrib/humanize/templatetags
copying django/contrib/humanize/templatetags/humanize.py -> build/lib/django/contrib/humanize/templatetags
copying django/contrib/humanize/templatetags/__init__.py -> build/lib/django/contrib/humanize/templatetags
creating build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/srs.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/ogrinspect.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/ogrinfo.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/layermapping.py -> build/lib/django/contrib/gis/utils
copying django/contrib/gis/utils/__init__.py -> build/lib/django/contrib/gis/utils
creating build/lib/django/contrib/gis/sitemaps
copying django/contrib/gis/sitemaps/views.py -> build/lib/django/contrib/gis/sitemaps
copying django/contrib/gis/sitemaps/kml.py -> build/lib/django/contrib/gis/sitemaps
copying django/contrib/gis/sitemaps/__init__.py -> build/lib/django/contrib/gis/sitemaps
creating build/lib/django/contrib/gis/serializers
copying django/contrib/gis/serializers/geojson.py -> build/lib/django/contrib/gis/serializers
copying django/contrib/gis/serializers/__init__.py -> build/lib/django/contrib/gis/serializers
creating build/lib/django/contrib/gis/management
copying django/contrib/gis/management/__init__.py -> build/lib/django/contrib/gis/management
creating build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/prepared.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/polygon.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/point.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/mutable_list.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/linestring.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/libgeos.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/io.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/geometry.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/factory.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/error.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/coordseq.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/collections.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/base.py -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/geos/__init__.py -> build/lib/django/contrib/gis/geos
creating build/lib/django/contrib/gis/geoip2
copying django/contrib/gis/geoip2/resources.py -> build/lib/django/contrib/gis/geoip2
copying django/contrib/gis/geoip2/base.py -> build/lib/django/contrib/gis/geoip2
copying django/contrib/gis/geoip2/__init__.py -> build/lib/django/contrib/gis/geoip2
creating build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/srs.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/libgdal.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/layer.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/geomtype.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/geometries.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/field.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/feature.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/error.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/envelope.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/driver.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/datasource.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/base.py -> build/lib/django/contrib/gis/gdal
copying django/contrib/gis/gdal/__init__.py -> build/lib/django/contrib/gis/gdal
creating build/lib/django/contrib/gis/forms
copying django/contrib/gis/forms/widgets.py -> build/lib/django/contrib/gis/forms
copying django/contrib/gis/forms/fields.py -> build/lib/django/contrib/gis/forms
copying django/contrib/gis/forms/__init__.py -> build/lib/django/contrib/gis/forms
creating build/lib/django/contrib/gis/db
copying django/contrib/gis/db/__init__.py -> build/lib/django/contrib/gis/db
creating build/lib/django/contrib/gis/admin
copying django/contrib/gis/admin/widgets.py -> build/lib/django/contrib/gis/admin
copying django/contrib/gis/admin/options.py -> build/lib/django/contrib/gis/admin
copying django/contrib/gis/admin/__init__.py -> build/lib/django/contrib/gis/admin
creating build/lib/django/contrib/gis/management/commands
copying django/contrib/gis/management/commands/ogrinspect.py -> build/lib/django/contrib/gis/management/commands
copying django/contrib/gis/management/commands/inspectdb.py -> build/lib/django/contrib/gis/management/commands
copying django/contrib/gis/management/commands/__init__.py -> build/lib/django/contrib/gis/management/commands
creating build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/topology.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/threadsafe.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/prepared.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/predicates.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/misc.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/io.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/geom.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/errcheck.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/coordseq.py -> build/lib/django/contrib/gis/geos/prototypes
copying django/contrib/gis/geos/prototypes/__init__.py -> build/lib/django/contrib/gis/geos/prototypes
creating build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/source.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/const.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/base.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/band.py -> build/lib/django/contrib/gis/gdal/raster
copying django/contrib/gis/gdal/raster/__init__.py -> build/lib/django/contrib/gis/gdal/raster
creating build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/srs.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/raster.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/geom.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/generation.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/errcheck.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/ds.py -> build/lib/django/contrib/gis/gdal/prototypes
copying django/contrib/gis/gdal/prototypes/__init__.py -> build/lib/django/contrib/gis/gdal/prototypes
creating build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/proxy.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/lookups.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/functions.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/fields.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/aggregates.py -> build/lib/django/contrib/gis/db/models
copying django/contrib/gis/db/models/__init__.py -> build/lib/django/contrib/gis/db/models
creating build/lib/django/contrib/gis/db/backends
copying django/contrib/gis/db/backends/utils.py -> build/lib/django/contrib/gis/db/backends
copying django/contrib/gis/db/backends/__init__.py -> build/lib/django/contrib/gis/db/backends
creating build/lib/django/contrib/gis/db/models/sql
copying django/contrib/gis/db/models/sql/conversion.py -> build/lib/django/contrib/gis/db/models/sql
copying django/contrib/gis/db/models/sql/__init__.py -> build/lib/django/contrib/gis/db/models/sql
creating build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/schema.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/operations.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/models.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/introspection.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/features.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/client.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/base.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/adapter.py -> build/lib/django/contrib/gis/db/backends/spatialite
copying django/contrib/gis/db/backends/spatialite/__init__.py -> build/lib/django/contrib/gis/db/backends/spatialite
creating build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/schema.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/pgraster.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/operations.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/models.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/introspection.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/features.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/const.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/base.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/adapter.py -> build/lib/django/contrib/gis/db/backends/postgis
copying django/contrib/gis/db/backends/postgis/__init__.py -> build/lib/django/contrib/gis/db/backends/postgis
creating build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/schema.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/operations.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/models.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/introspection.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/features.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/base.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/adapter.py -> build/lib/django/contrib/gis/db/backends/oracle
copying django/contrib/gis/db/backends/oracle/__init__.py -> build/lib/django/contrib/gis/db/backends/oracle
creating build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/schema.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/operations.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/introspection.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/features.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/base.py -> build/lib/django/contrib/gis/db/backends/mysql
copying django/contrib/gis/db/backends/mysql/__init__.py -> build/lib/django/contrib/gis/db/backends/mysql
creating build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/operations.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/models.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/features.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/adapter.py -> build/lib/django/contrib/gis/db/backends/base
copying django/contrib/gis/db/backends/base/__init__.py -> build/lib/django/contrib/gis/db/backends/base
creating build/lib/django/contrib/flatpages/templatetags
copying django/contrib/flatpages/templatetags/flatpages.py -> build/lib/django/contrib/flatpages/templatetags
copying django/contrib/flatpages/templatetags/__init__.py -> build/lib/django/contrib/flatpages/templatetags
creating build/lib/django/contrib/flatpages/migrations
copying django/contrib/flatpages/migrations/__init__.py -> build/lib/django/contrib/flatpages/migrations
copying django/contrib/flatpages/migrations/0001_initial.py -> build/lib/django/contrib/flatpages/migrations
creating build/lib/django/contrib/contenttypes/migrations
copying django/contrib/contenttypes/migrations/__init__.py -> build/lib/django/contrib/contenttypes/migrations
copying django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/lib/django/contrib/contenttypes/migrations
copying django/contrib/contenttypes/migrations/0001_initial.py -> build/lib/django/contrib/contenttypes/migrations
creating build/lib/django/contrib/contenttypes/management
copying django/contrib/contenttypes/management/__init__.py -> build/lib/django/contrib/contenttypes/management
creating build/lib/django/contrib/contenttypes/management/commands
copying django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/lib/django/contrib/contenttypes/management/commands
copying django/contrib/contenttypes/management/commands/__init__.py -> build/lib/django/contrib/contenttypes/management/commands
creating build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/__init__.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/lib/django/contrib/auth/migrations
copying django/contrib/auth/migrations/0001_initial.py -> build/lib/django/contrib/auth/migrations
creating build/lib/django/contrib/auth/management
copying django/contrib/auth/management/__init__.py -> build/lib/django/contrib/auth/management
creating build/lib/django/contrib/auth/handlers
copying django/contrib/auth/handlers/modwsgi.py -> build/lib/django/contrib/auth/handlers
copying django/contrib/auth/handlers/__init__.py -> build/lib/django/contrib/auth/handlers
creating build/lib/django/contrib/auth/management/commands
copying django/contrib/auth/management/commands/createsuperuser.py -> build/lib/django/contrib/auth/management/commands
copying django/contrib/auth/management/commands/changepassword.py -> build/lib/django/contrib/auth/management/commands
copying django/contrib/auth/management/commands/__init__.py -> build/lib/django/contrib/auth/management/commands
creating build/lib/django/contrib/admin/views
copying django/contrib/admin/views/main.py -> build/lib/django/contrib/admin/views
copying django/contrib/admin/views/decorators.py -> build/lib/django/contrib/admin/views
copying django/contrib/admin/views/autocomplete.py -> build/lib/django/contrib/admin/views
copying django/contrib/admin/views/__init__.py -> build/lib/django/contrib/admin/views
creating build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/log.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/base.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/admin_urls.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/admin_modify.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/admin_list.py -> build/lib/django/contrib/admin/templatetags
copying django/contrib/admin/templatetags/__init__.py -> build/lib/django/contrib/admin/templatetags
creating build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/__init__.py -> build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/lib/django/contrib/admin/migrations
copying django/contrib/admin/migrations/0001_initial.py -> build/lib/django/contrib/admin/migrations
creating build/lib/django/conf/urls
copying django/conf/urls/static.py -> build/lib/django/conf/urls
copying django/conf/urls/i18n.py -> build/lib/django/conf/urls
copying django/conf/urls/__init__.py -> build/lib/django/conf/urls
creating build/lib/django/conf/locale
copying django/conf/locale/__init__.py -> build/lib/django/conf/locale
creating build/lib/django/conf/locale/zh_Hant
copying django/conf/locale/zh_Hant/formats.py -> build/lib/django/conf/locale/zh_Hant
copying django/conf/locale/zh_Hant/__init__.py -> build/lib/django/conf/locale/zh_Hant
creating build/lib/django/conf/locale/zh_Hans
copying django/conf/locale/zh_Hans/formats.py -> build/lib/django/conf/locale/zh_Hans
copying django/conf/locale/zh_Hans/__init__.py -> build/lib/django/conf/locale/zh_Hans
creating build/lib/django/conf/locale/vi
copying django/conf/locale/vi/formats.py -> build/lib/django/conf/locale/vi
copying django/conf/locale/vi/__init__.py -> build/lib/django/conf/locale/vi
creating build/lib/django/conf/locale/uz
copying django/conf/locale/uz/formats.py -> build/lib/django/conf/locale/uz
copying django/conf/locale/uz/__init__.py -> build/lib/django/conf/locale/uz
creating build/lib/django/conf/locale/uk
copying django/conf/locale/uk/formats.py -> build/lib/django/conf/locale/uk
copying django/conf/locale/uk/__init__.py -> build/lib/django/conf/locale/uk
creating build/lib/django/conf/locale/tr
copying django/conf/locale/tr/formats.py -> build/lib/django/conf/locale/tr
copying django/conf/locale/tr/__init__.py -> build/lib/django/conf/locale/tr
creating build/lib/django/conf/locale/tk
copying django/conf/locale/tk/formats.py -> build/lib/django/conf/locale/tk
copying django/conf/locale/tk/__init__.py -> build/lib/django/conf/locale/tk
creating build/lib/django/conf/locale/th
copying django/conf/locale/th/formats.py -> build/lib/django/conf/locale/th
copying django/conf/locale/th/__init__.py -> build/lib/django/conf/locale/th
creating build/lib/django/conf/locale/tg
copying django/conf/locale/tg/formats.py -> build/lib/django/conf/locale/tg
copying django/conf/locale/tg/__init__.py -> build/lib/django/conf/locale/tg
creating build/lib/django/conf/locale/te
copying django/conf/locale/te/formats.py -> build/lib/django/conf/locale/te
copying django/conf/locale/te/__init__.py -> build/lib/django/conf/locale/te
creating build/lib/django/conf/locale/ta
copying django/conf/locale/ta/formats.py -> build/lib/django/conf/locale/ta
copying django/conf/locale/ta/__init__.py -> build/lib/django/conf/locale/ta
creating build/lib/django/conf/locale/sv
copying django/conf/locale/sv/formats.py -> build/lib/django/conf/locale/sv
copying django/conf/locale/sv/__init__.py -> build/lib/django/conf/locale/sv
creating build/lib/django/conf/locale/sr_Latn
copying django/conf/locale/sr_Latn/formats.py -> build/lib/django/conf/locale/sr_Latn
copying django/conf/locale/sr_Latn/__init__.py -> build/lib/django/conf/locale/sr_Latn
creating build/lib/django/conf/locale/sr
copying django/conf/locale/sr/formats.py -> build/lib/django/conf/locale/sr
copying django/conf/locale/sr/__init__.py -> build/lib/django/conf/locale/sr
creating build/lib/django/conf/locale/sq
copying django/conf/locale/sq/formats.py -> build/lib/django/conf/locale/sq
copying django/conf/locale/sq/__init__.py -> build/lib/django/conf/locale/sq
creating build/lib/django/conf/locale/sl
copying django/conf/locale/sl/formats.py -> build/lib/django/conf/locale/sl
copying django/conf/locale/sl/__init__.py -> build/lib/django/conf/locale/sl
creating build/lib/django/conf/locale/sk
copying django/conf/locale/sk/formats.py -> build/lib/django/conf/locale/sk
copying django/conf/locale/sk/__init__.py -> build/lib/django/conf/locale/sk
creating build/lib/django/conf/locale/ru
copying django/conf/locale/ru/formats.py -> build/lib/django/conf/locale/ru
copying django/conf/locale/ru/__init__.py -> build/lib/django/conf/locale/ru
creating build/lib/django/conf/locale/ro
copying django/conf/locale/ro/formats.py -> build/lib/django/conf/locale/ro
copying django/conf/locale/ro/__init__.py -> build/lib/django/conf/locale/ro
creating build/lib/django/conf/locale/pt_BR
copying django/conf/locale/pt_BR/formats.py -> build/lib/django/conf/locale/pt_BR
copying django/conf/locale/pt_BR/__init__.py -> build/lib/django/conf/locale/pt_BR
creating build/lib/django/conf/locale/pt
copying django/conf/locale/pt/formats.py -> build/lib/django/conf/locale/pt
copying django/conf/locale/pt/__init__.py -> build/lib/django/conf/locale/pt
creating build/lib/django/conf/locale/pl
copying django/conf/locale/pl/formats.py -> build/lib/django/conf/locale/pl
copying django/conf/locale/pl/__init__.py -> build/lib/django/conf/locale/pl
creating build/lib/django/conf/locale/nn
copying django/conf/locale/nn/formats.py -> build/lib/django/conf/locale/nn
copying django/conf/locale/nn/__init__.py -> build/lib/django/conf/locale/nn
creating build/lib/django/conf/locale/nl
copying django/conf/locale/nl/formats.py -> build/lib/django/conf/locale/nl
copying django/conf/locale/nl/__init__.py -> build/lib/django/conf/locale/nl
creating build/lib/django/conf/locale/nb
copying django/conf/locale/nb/formats.py -> build/lib/django/conf/locale/nb
copying django/conf/locale/nb/__init__.py -> build/lib/django/conf/locale/nb
creating build/lib/django/conf/locale/ms
copying django/conf/locale/ms/formats.py -> build/lib/django/conf/locale/ms
copying django/conf/locale/ms/__init__.py -> build/lib/django/conf/locale/ms
creating build/lib/django/conf/locale/mn
copying django/conf/locale/mn/formats.py -> build/lib/django/conf/locale/mn
copying django/conf/locale/mn/__init__.py -> build/lib/django/conf/locale/mn
creating build/lib/django/conf/locale/ml
copying django/conf/locale/ml/formats.py -> build/lib/django/conf/locale/ml
copying django/conf/locale/ml/__init__.py -> build/lib/django/conf/locale/ml
creating build/lib/django/conf/locale/mk
copying django/conf/locale/mk/formats.py -> build/lib/django/conf/locale/mk
copying django/conf/locale/mk/__init__.py -> build/lib/django/conf/locale/mk
creating build/lib/django/conf/locale/lv
copying django/conf/locale/lv/formats.py -> build/lib/django/conf/locale/lv
copying django/conf/locale/lv/__init__.py -> build/lib/django/conf/locale/lv
creating build/lib/django/conf/locale/lt
copying django/conf/locale/lt/formats.py -> build/lib/django/conf/locale/lt
copying django/conf/locale/lt/__init__.py -> build/lib/django/conf/locale/lt
creating build/lib/django/conf/locale/ky
copying django/conf/locale/ky/formats.py -> build/lib/django/conf/locale/ky
copying django/conf/locale/ky/__init__.py -> build/lib/django/conf/locale/ky
creating build/lib/django/conf/locale/ko
copying django/conf/locale/ko/formats.py -> build/lib/django/conf/locale/ko
copying django/conf/locale/ko/__init__.py -> build/lib/django/conf/locale/ko
creating build/lib/django/conf/locale/kn
copying django/conf/locale/kn/formats.py -> build/lib/django/conf/locale/kn
copying django/conf/locale/kn/__init__.py -> build/lib/django/conf/locale/kn
creating build/lib/django/conf/locale/km
copying django/conf/locale/km/formats.py -> build/lib/django/conf/locale/km
copying django/conf/locale/km/__init__.py -> build/lib/django/conf/locale/km
creating build/lib/django/conf/locale/ka
copying django/conf/locale/ka/formats.py -> build/lib/django/conf/locale/ka
copying django/conf/locale/ka/__init__.py -> build/lib/django/conf/locale/ka
creating build/lib/django/conf/locale/ja
copying django/conf/locale/ja/formats.py -> build/lib/django/conf/locale/ja
copying django/conf/locale/ja/__init__.py -> build/lib/django/conf/locale/ja
creating build/lib/django/conf/locale/it
copying django/conf/locale/it/formats.py -> build/lib/django/conf/locale/it
copying django/conf/locale/it/__init__.py -> build/lib/django/conf/locale/it
creating build/lib/django/conf/locale/is
copying django/conf/locale/is/formats.py -> build/lib/django/conf/locale/is
copying django/conf/locale/is/__init__.py -> build/lib/django/conf/locale/is
creating build/lib/django/conf/locale/ig
copying django/conf/locale/ig/formats.py -> build/lib/django/conf/locale/ig
copying django/conf/locale/ig/__init__.py -> build/lib/django/conf/locale/ig
creating build/lib/django/conf/locale/id
copying django/conf/locale/id/formats.py -> build/lib/django/conf/locale/id
copying django/conf/locale/id/__init__.py -> build/lib/django/conf/locale/id
creating build/lib/django/conf/locale/hu
copying django/conf/locale/hu/formats.py -> build/lib/django/conf/locale/hu
copying django/conf/locale/hu/__init__.py -> build/lib/django/conf/locale/hu
creating build/lib/django/conf/locale/hr
copying django/conf/locale/hr/formats.py -> build/lib/django/conf/locale/hr
copying django/conf/locale/hr/__init__.py -> build/lib/django/conf/locale/hr
creating build/lib/django/conf/locale/hi
copying django/conf/locale/hi/formats.py -> build/lib/django/conf/locale/hi
copying django/conf/locale/hi/__init__.py -> build/lib/django/conf/locale/hi
creating build/lib/django/conf/locale/he
copying django/conf/locale/he/formats.py -> build/lib/django/conf/locale/he
copying django/conf/locale/he/__init__.py -> build/lib/django/conf/locale/he
creating build/lib/django/conf/locale/gl
copying django/conf/locale/gl/formats.py -> build/lib/django/conf/locale/gl
copying django/conf/locale/gl/__init__.py -> build/lib/django/conf/locale/gl
creating build/lib/django/conf/locale/gd
copying django/conf/locale/gd/formats.py -> build/lib/django/conf/locale/gd
copying django/conf/locale/gd/__init__.py -> build/lib/django/conf/locale/gd
creating build/lib/django/conf/locale/ga
copying django/conf/locale/ga/formats.py -> build/lib/django/conf/locale/ga
copying django/conf/locale/ga/__init__.py -> build/lib/django/conf/locale/ga
creating build/lib/django/conf/locale/fy
copying django/conf/locale/fy/formats.py -> build/lib/django/conf/locale/fy
copying django/conf/locale/fy/__init__.py -> build/lib/django/conf/locale/fy
creating build/lib/django/conf/locale/fr
copying django/conf/locale/fr/formats.py -> build/lib/django/conf/locale/fr
copying django/conf/locale/fr/__init__.py -> build/lib/django/conf/locale/fr
creating build/lib/django/conf/locale/fi
copying django/conf/locale/fi/formats.py -> build/lib/django/conf/locale/fi
copying django/conf/locale/fi/__init__.py -> build/lib/django/conf/locale/fi
creating build/lib/django/conf/locale/fa
copying django/conf/locale/fa/formats.py -> build/lib/django/conf/locale/fa
copying django/conf/locale/fa/__init__.py -> build/lib/django/conf/locale/fa
creating build/lib/django/conf/locale/eu
copying django/conf/locale/eu/formats.py -> build/lib/django/conf/locale/eu
copying django/conf/locale/eu/__init__.py -> build/lib/django/conf/locale/eu
creating build/lib/django/conf/locale/et
copying django/conf/locale/et/formats.py -> build/lib/django/conf/locale/et
copying django/conf/locale/et/__init__.py -> build/lib/django/conf/locale/et
creating build/lib/django/conf/locale/es_PR
copying django/conf/locale/es_PR/formats.py -> build/lib/django/conf/locale/es_PR
copying django/conf/locale/es_PR/__init__.py -> build/lib/django/conf/locale/es_PR
creating build/lib/django/conf/locale/es_NI
copying django/conf/locale/es_NI/formats.py -> build/lib/django/conf/locale/es_NI
copying django/conf/locale/es_NI/__init__.py -> build/lib/django/conf/locale/es_NI
creating build/lib/django/conf/locale/es_MX
copying django/conf/locale/es_MX/formats.py -> build/lib/django/conf/locale/es_MX
copying django/conf/locale/es_MX/__init__.py -> build/lib/django/conf/locale/es_MX
creating build/lib/django/conf/locale/es_CO
copying django/conf/locale/es_CO/formats.py -> build/lib/django/conf/locale/es_CO
copying django/conf/locale/es_CO/__init__.py -> build/lib/django/conf/locale/es_CO
creating build/lib/django/conf/locale/es_AR
copying django/conf/locale/es_AR/formats.py -> build/lib/django/conf/locale/es_AR
copying django/conf/locale/es_AR/__init__.py -> build/lib/django/conf/locale/es_AR
creating build/lib/django/conf/locale/es
copying django/conf/locale/es/formats.py -> build/lib/django/conf/locale/es
copying django/conf/locale/es/__init__.py -> build/lib/django/conf/locale/es
creating build/lib/django/conf/locale/eo
copying django/conf/locale/eo/formats.py -> build/lib/django/conf/locale/eo
copying django/conf/locale/eo/__init__.py -> build/lib/django/conf/locale/eo
creating build/lib/django/conf/locale/en_GB
copying django/conf/locale/en_GB/formats.py -> build/lib/django/conf/locale/en_GB
copying django/conf/locale/en_GB/__init__.py -> build/lib/django/conf/locale/en_GB
creating build/lib/django/conf/locale/en_AU
copying django/conf/locale/en_AU/formats.py -> build/lib/django/conf/locale/en_AU
copying django/conf/locale/en_AU/__init__.py -> build/lib/django/conf/locale/en_AU
creating build/lib/django/conf/locale/en
copying django/conf/locale/en/formats.py -> build/lib/django/conf/locale/en
copying django/conf/locale/en/__init__.py -> build/lib/django/conf/locale/en
creating build/lib/django/conf/locale/el
copying django/conf/locale/el/formats.py -> build/lib/django/conf/locale/el
copying django/conf/locale/el/__init__.py -> build/lib/django/conf/locale/el
creating build/lib/django/conf/locale/de_CH
copying django/conf/locale/de_CH/formats.py -> build/lib/django/conf/locale/de_CH
copying django/conf/locale/de_CH/__init__.py -> build/lib/django/conf/locale/de_CH
creating build/lib/django/conf/locale/de
copying django/conf/locale/de/formats.py -> build/lib/django/conf/locale/de
copying django/conf/locale/de/__init__.py -> build/lib/django/conf/locale/de
creating build/lib/django/conf/locale/da
copying django/conf/locale/da/formats.py -> build/lib/django/conf/locale/da
copying django/conf/locale/da/__init__.py -> build/lib/django/conf/locale/da
creating build/lib/django/conf/locale/cy
copying django/conf/locale/cy/formats.py -> build/lib/django/conf/locale/cy
copying django/conf/locale/cy/__init__.py -> build/lib/django/conf/locale/cy
creating build/lib/django/conf/locale/cs
copying django/conf/locale/cs/formats.py -> build/lib/django/conf/locale/cs
copying django/conf/locale/cs/__init__.py -> build/lib/django/conf/locale/cs
creating build/lib/django/conf/locale/ckb
copying django/conf/locale/ckb/formats.py -> build/lib/django/conf/locale/ckb
copying django/conf/locale/ckb/__init__.py -> build/lib/django/conf/locale/ckb
creating build/lib/django/conf/locale/ca
copying django/conf/locale/ca/formats.py -> build/lib/django/conf/locale/ca
copying django/conf/locale/ca/__init__.py -> build/lib/django/conf/locale/ca
creating build/lib/django/conf/locale/bs
copying django/conf/locale/bs/formats.py -> build/lib/django/conf/locale/bs
copying django/conf/locale/bs/__init__.py -> build/lib/django/conf/locale/bs
creating build/lib/django/conf/locale/bn
copying django/conf/locale/bn/formats.py -> build/lib/django/conf/locale/bn
copying django/conf/locale/bn/__init__.py -> build/lib/django/conf/locale/bn
creating build/lib/django/conf/locale/bg
copying django/conf/locale/bg/formats.py -> build/lib/django/conf/locale/bg
copying django/conf/locale/bg/__init__.py -> build/lib/django/conf/locale/bg
creating build/lib/django/conf/locale/az
copying django/conf/locale/az/formats.py -> build/lib/django/conf/locale/az
copying django/conf/locale/az/__init__.py -> build/lib/django/conf/locale/az
creating build/lib/django/conf/locale/ar_DZ
copying django/conf/locale/ar_DZ/formats.py -> build/lib/django/conf/locale/ar_DZ
copying django/conf/locale/ar_DZ/__init__.py -> build/lib/django/conf/locale/ar_DZ
creating build/lib/django/conf/locale/ar
copying django/conf/locale/ar/formats.py -> build/lib/django/conf/locale/ar
copying django/conf/locale/ar/__init__.py -> build/lib/django/conf/locale/ar
running egg_info
writing Django.egg-info/PKG-INFO
writing dependency_links to Django.egg-info/dependency_links.txt
writing entry points to Django.egg-info/entry_points.txt
writing requirements to Django.egg-info/requires.txt
writing top-level names to Django.egg-info/top_level.txt
reading manifest file 'Django.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'LICENSE.python'
adding license file 'AUTHORS'
writing manifest file 'Django.egg-info/SOURCES.txt'
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.app_template' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.app_template' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.app_template' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.app_template' to be distributed and are
already explicitly excluding 'django.conf.app_template' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.app_template.migrations' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.app_template.migrations' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.app_template.migrations' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.app_template.migrations' to be distributed and are
already explicitly excluding 'django.conf.app_template.migrations' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ig.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ig.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ig.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ig.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ig.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.kab.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.kab.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.kab.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.kab.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.conf.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.project_template' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.project_template' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.project_template' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.project_template' to be distributed and are
already explicitly excluding 'django.conf.project_template' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.conf.project_template.project_name' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.conf.project_template.project_name' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.conf.project_template.project_name' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.conf.project_template.project_name' to be distributed and are
already explicitly excluding 'django.conf.project_template.project_name' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.am.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.am.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.am.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.am.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.am.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.kab.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.kab.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.kab.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.kab.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admin.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.css' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.css' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.css' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.css' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.css' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.css.vendor.select2' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.css.vendor.select2' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.css.vendor.select2' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.css.vendor.select2' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.css.vendor.select2' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.img' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.img' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.img' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.img' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.img' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.img.gis' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.img.gis' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.img.gis' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.img.gis' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.img.gis' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.js' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.js' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.js' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.js' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.admin' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.js.admin' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.js.admin' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.js.admin' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.js.admin' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.jquery' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.js.vendor.jquery' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.js.vendor.jquery' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.js.vendor.jquery' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.jquery' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.js.vendor.select2' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.js.vendor.select2.i18n' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.js.vendor.select2.i18n' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.js.vendor.select2.i18n' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.select2.i18n' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.js.vendor.xregexp' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.static.admin.js.vendor.xregexp' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.static.admin.js.vendor.xregexp' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.static.admin.js.vendor.xregexp' to be distributed and are
already explicitly excluding 'django.contrib.admin.static.admin.js.vendor.xregexp' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.templates.admin' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.templates.admin' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.templates.admin' to be distributed and are
already explicitly excluding 'django.contrib.admin.templates.admin' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.auth.user' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.templates.admin.auth.user' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.templates.admin.auth.user' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.templates.admin.auth.user' to be distributed and are
already explicitly excluding 'django.contrib.admin.templates.admin.auth.user' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.edit_inline' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.templates.admin.edit_inline' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.templates.admin.edit_inline' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.templates.admin.edit_inline' to be distributed and are
already explicitly excluding 'django.contrib.admin.templates.admin.edit_inline' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.includes' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.templates.admin.includes' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.templates.admin.includes' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.templates.admin.includes' to be distributed and are
already explicitly excluding 'django.contrib.admin.templates.admin.includes' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.admin.widgets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.templates.admin.widgets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.templates.admin.widgets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.templates.admin.widgets' to be distributed and are
already explicitly excluding 'django.contrib.admin.templates.admin.widgets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.templates.registration' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admin.templates.registration' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admin.templates.registration' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admin.templates.registration' to be distributed and are
already explicitly excluding 'django.contrib.admin.templates.registration' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.kab.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.kab.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.kab.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.kab.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admindocs.templates.admin_doc' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.admindocs.templates.admin_doc' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.admindocs.templates.admin_doc' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.admindocs.templates.admin_doc' to be distributed and are
already explicitly excluding 'django.contrib.admindocs.templates.admin_doc' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.kab.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.kab.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.kab.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.kab.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.auth.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.templates.auth.widgets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.templates.auth.widgets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.templates.auth.widgets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.templates.auth.widgets' to be distributed and are
already explicitly excluding 'django.contrib.auth.templates.auth.widgets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.auth.templates.registration' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.auth.templates.registration' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.auth.templates.registration' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.auth.templates.registration' to be distributed and are
already explicitly excluding 'django.contrib.auth.templates.registration' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.contenttypes.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.flatpages.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.gis.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.css' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.static.gis.css' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.static.gis.css' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.static.gis.css' to be distributed and are
already explicitly excluding 'django.contrib.gis.static.gis.css' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.img' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.static.gis.img' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.static.gis.img' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.static.gis.img' to be distributed and are
already explicitly excluding 'django.contrib.gis.static.gis.img' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.static.gis.js' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.static.gis.js' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.static.gis.js' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.static.gis.js' to be distributed and are
already explicitly excluding 'django.contrib.gis.static.gis.js' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.templates.gis' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.templates.gis' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.templates.gis' to be distributed and are
already explicitly excluding 'django.contrib.gis.templates.gis' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis.admin' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.templates.gis.admin' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.templates.gis.admin' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.templates.gis.admin' to be distributed and are
already explicitly excluding 'django.contrib.gis.templates.gis.admin' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.gis.templates.gis.kml' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.gis.templates.gis.kml' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.gis.templates.gis.kml' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.gis.templates.gis.kml' to be distributed and are
already explicitly excluding 'django.contrib.gis.templates.gis.kml' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.humanize.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.jinja2.postgres.widgets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.jinja2.postgres.widgets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.jinja2.postgres.widgets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.jinja2.postgres.widgets' to be distributed and are
already explicitly excluding 'django.contrib.postgres.jinja2.postgres.widgets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.postgres.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.postgres.templates.postgres.widgets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.postgres.templates.postgres.widgets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.postgres.templates.postgres.widgets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.postgres.templates.postgres.widgets' to be distributed and are
already explicitly excluding 'django.contrib.postgres.templates.postgres.widgets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.kab.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.kab.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.kab.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.kab.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.redirects.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.kab.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.kab.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.kab.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.kab.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sessions.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sitemaps.templates' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sitemaps.templates' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sitemaps.templates' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sitemaps.templates' to be distributed and are
already explicitly excluding 'django.contrib.sitemaps.templates' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.af.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.af.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.af.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.af.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.af.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ar.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ar.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ar.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ar.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ar.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ar_DZ.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ast.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ast.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ast.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ast.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ast.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.az.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.az.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.az.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.az.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.az.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.be.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.be.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.be.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.be.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.be.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.bg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.bg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.bg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.bg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.bn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.bn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.bn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.bn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.br.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.br.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.br.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.br.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.br.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.bs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.bs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.bs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.bs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.bs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ca.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ca.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ca.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ca.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ca.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ckb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ckb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ckb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ckb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.cs.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.cs.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.cs.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.cs.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.cs.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.cy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.cy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.cy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.cy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.cy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.da.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.da.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.da.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.da.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.da.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.de.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.de.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.de.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.de.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.de.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.dsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.dsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.dsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.dsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.dsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.el.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.el.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.el.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.el.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.el.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.en.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.en.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.en.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.en.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.en_AU.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.en_AU.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.en_AU.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.en_AU.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.en_GB.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.en_GB.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.en_GB.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.en_GB.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.eo.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.eo.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.eo.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.eo.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.eo.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.es.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.es.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.es.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.es.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.es_AR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.es_AR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.es_AR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.es_AR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.es_CO.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.es_CO.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.es_CO.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.es_CO.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.es_MX.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.es_MX.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.es_MX.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.es_MX.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.es_VE.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.es_VE.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.es_VE.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.es_VE.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.et.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.et.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.et.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.et.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.et.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.eu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.eu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.eu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.eu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.eu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.fa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.fa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.fa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.fa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.fi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.fi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.fi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.fi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.fr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.fr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.fr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.fr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.fy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.fy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.fy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.fy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.fy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ga.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ga.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ga.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ga.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ga.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.gd.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.gd.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.gd.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.gd.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.gd.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.gl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.gl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.gl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.gl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.gl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.he.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.he.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.he.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.he.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.he.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.hi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.hi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.hi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.hi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.hr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.hr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.hr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.hr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hsb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.hsb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.hsb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.hsb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.hsb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hu.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.hu.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.hu.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.hu.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.hu.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.hy.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.hy.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.hy.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.hy.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.hy.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ia.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ia.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ia.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ia.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ia.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.id.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.id.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.id.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.id.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.id.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.io.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.io.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.io.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.io.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.io.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.is.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.is.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.is.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.is.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.is.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.it.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.it.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.it.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.it.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.it.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ja.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ja.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ja.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ja.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ja.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ka.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ka.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ka.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ka.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ka.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kab.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.kab.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.kab.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.kab.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.kab.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.kk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.kk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.kk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.kk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.km.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.km.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.km.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.km.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.km.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.kn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.kn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.kn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.kn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.kn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ko.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ko.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ko.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ko.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ko.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ky.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ky.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ky.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ky.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ky.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.lb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.lb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.lb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.lb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.lt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.lt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.lt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.lt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.lv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.lv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.lv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.lv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.lv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.mk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.mk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.mk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.mk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ml.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ml.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ml.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ml.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ml.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.mn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.mn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.mn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.mn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.mr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.mr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.mr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.mr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.mr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ms.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ms.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ms.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ms.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ms.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.my.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.my.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.my.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.my.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.my.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nb.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.nb.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.nb.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.nb.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.nb.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ne.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ne.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ne.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ne.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ne.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.nl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.nl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.nl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.nl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.nn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.nn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.nn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.nn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.nn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.os.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.os.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.os.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.os.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.os.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pa.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.pa.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.pa.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.pa.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.pa.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.pl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.pl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.pl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.pl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.pt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.pt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.pt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.pt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.pt_BR.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ro.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ro.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ro.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ro.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ro.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ru.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ru.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ru.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ru.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ru.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.sk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.sk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.sk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.sk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sl.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.sl.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.sl.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.sl.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.sl.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sq.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.sq.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.sq.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.sq.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.sq.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.sr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.sr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.sr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.sr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.sr_Latn.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sv.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.sv.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.sv.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.sv.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.sv.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.sw.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.sw.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.sw.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.sw.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.sw.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ta.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ta.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ta.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ta.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ta.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.te.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.te.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.te.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.te.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.te.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tg.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.tg.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.tg.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.tg.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.tg.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.th.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.th.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.th.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.th.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.th.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.tk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.tk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.tk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.tk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tr.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.tr.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.tr.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.tr.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.tr.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.tt.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.tt.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.tt.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.tt.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.tt.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.udm.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.udm.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.udm.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.udm.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.udm.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.uk.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.uk.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.uk.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.uk.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.uk.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.ur.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.ur.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.ur.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.ur.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.ur.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.uz.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.uz.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.uz.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.uz.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.uz.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.vi.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.vi.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.vi.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.vi.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.vi.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.zh_Hans.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' to be distributed and are
already explicitly excluding 'django.contrib.sites.locale.zh_Hant.LC_MESSAGES' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.jinja2.django.forms' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.jinja2.django.forms' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.jinja2.django.forms' to be distributed and are
already explicitly excluding 'django.forms.jinja2.django.forms' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.errors.dict' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.jinja2.django.forms.errors.dict' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.jinja2.django.forms.errors.dict' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.jinja2.django.forms.errors.dict' to be distributed and are
already explicitly excluding 'django.forms.jinja2.django.forms.errors.dict' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.errors.list' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.jinja2.django.forms.errors.list' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.jinja2.django.forms.errors.list' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.jinja2.django.forms.errors.list' to be distributed and are
already explicitly excluding 'django.forms.jinja2.django.forms.errors.list' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.formsets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.jinja2.django.forms.formsets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.jinja2.django.forms.formsets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.jinja2.django.forms.formsets' to be distributed and are
already explicitly excluding 'django.forms.jinja2.django.forms.formsets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.jinja2.django.forms.widgets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.jinja2.django.forms.widgets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.jinja2.django.forms.widgets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.jinja2.django.forms.widgets' to be distributed and are
already explicitly excluding 'django.forms.jinja2.django.forms.widgets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.templates.django.forms' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.templates.django.forms' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.templates.django.forms' to be distributed and are
already explicitly excluding 'django.forms.templates.django.forms' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.errors.dict' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.templates.django.forms.errors.dict' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.templates.django.forms.errors.dict' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.templates.django.forms.errors.dict' to be distributed and are
already explicitly excluding 'django.forms.templates.django.forms.errors.dict' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.errors.list' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.templates.django.forms.errors.list' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.templates.django.forms.errors.list' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.templates.django.forms.errors.list' to be distributed and are
already explicitly excluding 'django.forms.templates.django.forms.errors.list' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.formsets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.templates.django.forms.formsets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.templates.django.forms.formsets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.templates.django.forms.formsets' to be distributed and are
already explicitly excluding 'django.forms.templates.django.forms.formsets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.forms.templates.django.forms.widgets' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.forms.templates.django.forms.widgets' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.forms.templates.django.forms.widgets' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.forms.templates.django.forms.widgets' to be distributed and are
already explicitly excluding 'django.forms.templates.django.forms.widgets' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.views.templates' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'django.views.templates' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'django.views.templates' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'django.views.templates' to be distributed and are
already explicitly excluding 'django.views.templates' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
creating build/lib/django/views/templates
copying django/views/templates/default_urlconf.html -> build/lib/django/views/templates
copying django/views/templates/technical_404.html -> build/lib/django/views/templates
copying django/views/templates/technical_500.html -> build/lib/django/views/templates
copying django/views/templates/technical_500.txt -> build/lib/django/views/templates
creating build/lib/django/forms/jinja2
creating build/lib/django/forms/jinja2/django
creating build/lib/django/forms/jinja2/django/forms
copying django/forms/jinja2/django/forms/attrs.html -> build/lib/django/forms/jinja2/django/forms
copying django/forms/jinja2/django/forms/default.html -> build/lib/django/forms/jinja2/django/forms
copying django/forms/jinja2/django/forms/div.html -> build/lib/django/forms/jinja2/django/forms
copying django/forms/jinja2/django/forms/label.html -> build/lib/django/forms/jinja2/django/forms
copying django/forms/jinja2/django/forms/p.html -> build/lib/django/forms/jinja2/django/forms
copying django/forms/jinja2/django/forms/table.html -> build/lib/django/forms/jinja2/django/forms
copying django/forms/jinja2/django/forms/ul.html -> build/lib/django/forms/jinja2/django/forms
creating build/lib/django/forms/jinja2/django/forms/errors
creating build/lib/django/forms/jinja2/django/forms/errors/dict
copying django/forms/jinja2/django/forms/errors/dict/default.html -> build/lib/django/forms/jinja2/django/forms/errors/dict
copying django/forms/jinja2/django/forms/errors/dict/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/dict
copying django/forms/jinja2/django/forms/errors/dict/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/dict
creating build/lib/django/forms/jinja2/django/forms/errors/list
copying django/forms/jinja2/django/forms/errors/list/default.html -> build/lib/django/forms/jinja2/django/forms/errors/list
copying django/forms/jinja2/django/forms/errors/list/text.txt -> build/lib/django/forms/jinja2/django/forms/errors/list
copying django/forms/jinja2/django/forms/errors/list/ul.html -> build/lib/django/forms/jinja2/django/forms/errors/list
creating build/lib/django/forms/jinja2/django/forms/formsets
copying django/forms/jinja2/django/forms/formsets/default.html -> build/lib/django/forms/jinja2/django/forms/formsets
copying django/forms/jinja2/django/forms/formsets/div.html -> build/lib/django/forms/jinja2/django/forms/formsets
copying django/forms/jinja2/django/forms/formsets/p.html -> build/lib/django/forms/jinja2/django/forms/formsets
copying django/forms/jinja2/django/forms/formsets/table.html -> build/lib/django/forms/jinja2/django/forms/formsets
copying django/forms/jinja2/django/forms/formsets/ul.html -> build/lib/django/forms/jinja2/django/forms/formsets
creating build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/attrs.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/checkbox.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/date.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/datetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/email.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/file.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/input.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/input_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/number.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/password.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/radio.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/radio_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/select.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/select_date.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/select_option.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/text.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/textarea.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/time.html -> build/lib/django/forms/jinja2/django/forms/widgets
copying django/forms/jinja2/django/forms/widgets/url.html -> build/lib/django/forms/jinja2/django/forms/widgets
creating build/lib/django/forms/templates
creating build/lib/django/forms/templates/django
creating build/lib/django/forms/templates/django/forms
copying django/forms/templates/django/forms/attrs.html -> build/lib/django/forms/templates/django/forms
copying django/forms/templates/django/forms/default.html -> build/lib/django/forms/templates/django/forms
copying django/forms/templates/django/forms/div.html -> build/lib/django/forms/templates/django/forms
copying django/forms/templates/django/forms/label.html -> build/lib/django/forms/templates/django/forms
copying django/forms/templates/django/forms/p.html -> build/lib/django/forms/templates/django/forms
copying django/forms/templates/django/forms/table.html -> build/lib/django/forms/templates/django/forms
copying django/forms/templates/django/forms/ul.html -> build/lib/django/forms/templates/django/forms
creating build/lib/django/forms/templates/django/forms/errors
creating build/lib/django/forms/templates/django/forms/errors/dict
copying django/forms/templates/django/forms/errors/dict/default.html -> build/lib/django/forms/templates/django/forms/errors/dict
copying django/forms/templates/django/forms/errors/dict/text.txt -> build/lib/django/forms/templates/django/forms/errors/dict
copying django/forms/templates/django/forms/errors/dict/ul.html -> build/lib/django/forms/templates/django/forms/errors/dict
creating build/lib/django/forms/templates/django/forms/errors/list
copying django/forms/templates/django/forms/errors/list/default.html -> build/lib/django/forms/templates/django/forms/errors/list
copying django/forms/templates/django/forms/errors/list/text.txt -> build/lib/django/forms/templates/django/forms/errors/list
copying django/forms/templates/django/forms/errors/list/ul.html -> build/lib/django/forms/templates/django/forms/errors/list
creating build/lib/django/forms/templates/django/forms/formsets
copying django/forms/templates/django/forms/formsets/default.html -> build/lib/django/forms/templates/django/forms/formsets
copying django/forms/templates/django/forms/formsets/div.html -> build/lib/django/forms/templates/django/forms/formsets
copying django/forms/templates/django/forms/formsets/p.html -> build/lib/django/forms/templates/django/forms/formsets
copying django/forms/templates/django/forms/formsets/table.html -> build/lib/django/forms/templates/django/forms/formsets
copying django/forms/templates/django/forms/formsets/ul.html -> build/lib/django/forms/templates/django/forms/formsets
creating build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/attrs.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/checkbox.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/checkbox_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/checkbox_select.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/date.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/datetime.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/email.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/file.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/hidden.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/input.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/input_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/multiple_input.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/multiwidget.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/number.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/password.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/radio.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/radio_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/select.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/select_date.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/select_option.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/splitdatetime.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/text.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/textarea.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/time.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/forms/templates/django/forms/widgets/url.html -> build/lib/django/forms/templates/django/forms/widgets
copying django/dispatch/license.txt -> build/lib/django/dispatch
creating build/lib/django/conf/app_template
copying django/conf/app_template/__init__.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/admin.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/apps.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/models.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/tests.py-tpl -> build/lib/django/conf/app_template
copying django/conf/app_template/views.py-tpl -> build/lib/django/conf/app_template
creating build/lib/django/conf/app_template/migrations
copying django/conf/app_template/migrations/__init__.py-tpl -> build/lib/django/conf/app_template/migrations
creating build/lib/django/conf/project_template
copying django/conf/project_template/manage.py-tpl -> build/lib/django/conf/project_template
creating build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/__init__.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/asgi.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/settings.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/urls.py-tpl -> build/lib/django/conf/project_template/project_name
copying django/conf/project_template/project_name/wsgi.py-tpl -> build/lib/django/conf/project_template/project_name
creating build/lib/django/contrib/sites/locale
creating build/lib/django/contrib/sites/locale/af
creating build/lib/django/contrib/sites/locale/af/LC_MESSAGES
copying django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
copying django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/af/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ar
creating build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
copying django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
copying django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ar_DZ
creating build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ast
creating build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
copying django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
copying django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/az
creating build/lib/django/contrib/sites/locale/az/LC_MESSAGES
copying django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
copying django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/az/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/be
creating build/lib/django/contrib/sites/locale/be/LC_MESSAGES
copying django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
copying django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/be/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/bg
creating build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
copying django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
copying django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/bn
creating build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
copying django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
copying django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/br
creating build/lib/django/contrib/sites/locale/br/LC_MESSAGES
copying django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
copying django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/br/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/bs
creating build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
copying django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
copying django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ca
creating build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
copying django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
copying django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ckb
creating build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
copying django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/cs
creating build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
copying django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
copying django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/cy
creating build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
copying django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
copying django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/da
creating build/lib/django/contrib/sites/locale/da/LC_MESSAGES
copying django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
copying django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/da/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/de
creating build/lib/django/contrib/sites/locale/de/LC_MESSAGES
copying django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
copying django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/de/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/dsb
creating build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/el
creating build/lib/django/contrib/sites/locale/el/LC_MESSAGES
copying django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
copying django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/el/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/en
creating build/lib/django/contrib/sites/locale/en/LC_MESSAGES
copying django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
copying django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/en_AU
creating build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/en_GB
creating build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/eo
creating build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
copying django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
copying django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es
creating build/lib/django/contrib/sites/locale/es/LC_MESSAGES
copying django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
copying django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_AR
creating build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_CO
creating build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_MX
creating build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/es_VE
creating build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/et
creating build/lib/django/contrib/sites/locale/et/LC_MESSAGES
copying django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
copying django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/et/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/eu
creating build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
copying django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
copying django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fa
creating build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
copying django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
copying django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fi
creating build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
copying django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
copying django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fr
creating build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
copying django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
copying django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/fy
creating build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
copying django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
copying django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ga
creating build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
copying django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
copying django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/gd
creating build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
copying django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
copying django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/gl
creating build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
copying django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
copying django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/he
creating build/lib/django/contrib/sites/locale/he/LC_MESSAGES
copying django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
copying django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/he/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hi
creating build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
copying django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
copying django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hr
creating build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
copying django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
copying django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hsb
creating build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hu
creating build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
copying django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
copying django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/hy
creating build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
copying django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
copying django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ia
creating build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
copying django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
copying django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/id
creating build/lib/django/contrib/sites/locale/id/LC_MESSAGES
copying django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
copying django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/id/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/io
creating build/lib/django/contrib/sites/locale/io/LC_MESSAGES
copying django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
copying django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/io/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/is
creating build/lib/django/contrib/sites/locale/is/LC_MESSAGES
copying django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
copying django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/is/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/it
creating build/lib/django/contrib/sites/locale/it/LC_MESSAGES
copying django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
copying django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/it/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ja
creating build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
copying django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
copying django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ka
creating build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
copying django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
copying django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/kab
creating build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
copying django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
copying django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/kk
creating build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
copying django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
copying django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/km
creating build/lib/django/contrib/sites/locale/km/LC_MESSAGES
copying django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
copying django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/km/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/kn
creating build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
copying django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
copying django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ko
creating build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
copying django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
copying django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ky
creating build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
copying django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
copying django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/lb
creating build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
copying django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
copying django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/lt
creating build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
copying django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
copying django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/lv
creating build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
copying django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
copying django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/mk
creating build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
copying django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
copying django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ml
creating build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
copying django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
copying django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/mn
creating build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
copying django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
copying django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/mr
creating build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
copying django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
copying django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ms
creating build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
copying django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
copying django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/my
creating build/lib/django/contrib/sites/locale/my/LC_MESSAGES
copying django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
copying django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/my/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/nb
creating build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
copying django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
copying django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ne
creating build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
copying django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
copying django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/nl
creating build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
copying django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
copying django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/nn
creating build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
copying django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
copying django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/os
creating build/lib/django/contrib/sites/locale/os/LC_MESSAGES
copying django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
copying django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/os/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pa
creating build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
copying django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
copying django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pl
creating build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
copying django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
copying django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pt
creating build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
copying django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
copying django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/pt_BR
creating build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ro
creating build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
copying django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
copying django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ru
creating build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
copying django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
copying django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sk
creating build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
copying django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
copying django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sl
creating build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
copying django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
copying django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sq
creating build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
copying django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
copying django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sr
creating build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
copying django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
copying django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sr_Latn
creating build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sv
creating build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
copying django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
copying django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/sw
creating build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
copying django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
copying django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ta
creating build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
copying django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
copying django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/te
creating build/lib/django/contrib/sites/locale/te/LC_MESSAGES
copying django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
copying django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/te/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tg
creating build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
copying django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
copying django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/th
creating build/lib/django/contrib/sites/locale/th/LC_MESSAGES
copying django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
copying django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/th/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tk
creating build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
copying django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
copying django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tr
creating build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
copying django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
copying django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/tt
creating build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
copying django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
copying django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/udm
creating build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
copying django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
copying django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/uk
creating build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
copying django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
copying django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/ur
creating build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
copying django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
copying django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/uz
creating build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
copying django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
copying django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/vi
creating build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
copying django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
copying django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/zh_Hans
creating build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/sites/locale/zh_Hant
creating build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/sitemaps/templates
copying django/contrib/sitemaps/templates/sitemap.xml -> build/lib/django/contrib/sitemaps/templates
copying django/contrib/sitemaps/templates/sitemap_index.xml -> build/lib/django/contrib/sitemaps/templates
creating build/lib/django/contrib/sessions/locale
creating build/lib/django/contrib/sessions/locale/af
creating build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
copying django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
copying django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/af/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ar
creating build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ar_DZ
creating build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ast
creating build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/az
creating build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
copying django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
copying django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/az/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/be
creating build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
copying django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
copying django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/be/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/bg
creating build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/bn
creating build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/br
creating build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
copying django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
copying django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/br/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/bs
creating build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ca
creating build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ckb
creating build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
copying django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/cs
creating build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/cy
creating build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/da
creating build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
copying django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
copying django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/da/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/de
creating build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
copying django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
copying django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/de/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/dsb
creating build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/el
creating build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
copying django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
copying django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/el/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/en
creating build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
copying django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
copying django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/en_AU
creating build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/en_GB
creating build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/eo
creating build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es
creating build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
copying django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
copying django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_AR
creating build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_CO
creating build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_MX
creating build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/es_VE
creating build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/et
creating build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
copying django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
copying django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/et/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/eu
creating build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fa
creating build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fi
creating build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fr
creating build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/fy
creating build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ga
creating build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/gd
creating build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/gl
creating build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/he
creating build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
copying django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
copying django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/he/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hi
creating build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hr
creating build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hsb
creating build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hu
creating build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/hy
creating build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ia
creating build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/id
creating build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
copying django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
copying django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/id/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/io
creating build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
copying django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
copying django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/io/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/is
creating build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
copying django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
copying django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/is/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/it
creating build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
copying django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
copying django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/it/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ja
creating build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ka
creating build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/kab
creating build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/kk
creating build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/km
creating build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
copying django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
copying django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/km/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/kn
creating build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ko
creating build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ky
creating build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/lb
creating build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/lt
creating build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/lv
creating build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/mk
creating build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ml
creating build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/mn
creating build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/mr
creating build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ms
creating build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
copying django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/my
creating build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
copying django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
copying django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/my/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/nb
creating build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ne
creating build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/nl
creating build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/nn
creating build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/os
creating build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
copying django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
copying django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/os/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pa
creating build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pl
creating build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pt
creating build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/pt_BR
creating build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ro
creating build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ru
creating build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sk
creating build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sl
creating build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sq
creating build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sr
creating build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sr_Latn
creating build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sv
creating build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/sw
creating build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ta
creating build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/te
creating build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
copying django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
copying django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/te/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tg
creating build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/th
creating build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
copying django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
copying django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/th/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tk
creating build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tr
creating build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/tt
creating build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/udm
creating build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/uk
creating build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/ur
creating build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/uz
creating build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/vi
creating build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/zh_Hans
creating build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/sessions/locale/zh_Hant
creating build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale
creating build/lib/django/contrib/redirects/locale/af
creating build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
copying django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
copying django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/af/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ar
creating build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ar_DZ
creating build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ast
creating build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/az
creating build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
copying django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
copying django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/az/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/be
creating build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
copying django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
copying django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/be/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/bg
creating build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/bn
creating build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/br
creating build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
copying django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
copying django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/br/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/bs
creating build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ca
creating build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ckb
creating build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
copying django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/cs
creating build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/cy
creating build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/da
creating build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
copying django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
copying django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/da/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/de
creating build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
copying django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
copying django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/de/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/dsb
creating build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/el
creating build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
copying django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
copying django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/el/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/en
creating build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
copying django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
copying django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/en_AU
creating build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/en_GB
creating build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/eo
creating build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es
creating build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
copying django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
copying django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_AR
creating build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_CO
creating build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_MX
creating build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/es_VE
creating build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/et
creating build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
copying django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
copying django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/et/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/eu
creating build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fa
creating build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fi
creating build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fr
creating build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/fy
creating build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ga
creating build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/gd
creating build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/gl
creating build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/he
creating build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
copying django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
copying django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/he/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hi
creating build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hr
creating build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hsb
creating build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hu
creating build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/hy
creating build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ia
creating build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/id
creating build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
copying django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
copying django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/id/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/io
creating build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
copying django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
copying django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/io/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/is
creating build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
copying django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
copying django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/is/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/it
creating build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
copying django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
copying django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/it/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ja
creating build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ka
creating build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/kab
creating build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/kk
creating build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/km
creating build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
copying django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
copying django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/km/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/kn
creating build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ko
creating build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ky
creating build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/lb
creating build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/lt
creating build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/lv
creating build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/mk
creating build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ml
creating build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/mn
creating build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/mr
creating build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ms
creating build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
copying django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/my
creating build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
copying django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
copying django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/my/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/nb
creating build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ne
creating build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/nl
creating build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/nn
creating build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/os
creating build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
copying django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
copying django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/os/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pa
creating build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pl
creating build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pt
creating build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/pt_BR
creating build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ro
creating build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ru
creating build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sk
creating build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sl
creating build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sq
creating build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sr
creating build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sr_Latn
creating build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sv
creating build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/sw
creating build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ta
creating build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/te
creating build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
copying django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
copying django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/te/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tg
creating build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/th
creating build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
copying django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
copying django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/th/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tk
creating build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tr
creating build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/tt
creating build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/udm
creating build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/uk
creating build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/ur
creating build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/uz
creating build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/vi
creating build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/zh_Hans
creating build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/redirects/locale/zh_Hant
creating build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/postgres/jinja2
creating build/lib/django/contrib/postgres/jinja2/postgres
creating build/lib/django/contrib/postgres/jinja2/postgres/widgets
copying django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/jinja2/postgres/widgets
creating build/lib/django/contrib/postgres/locale
creating build/lib/django/contrib/postgres/locale/af
creating build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
copying django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
copying django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/af/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ar
creating build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ar_DZ
creating build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/az
creating build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
copying django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
copying django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/az/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/be
creating build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
copying django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
copying django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/be/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/bg
creating build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ca
creating build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ckb
creating build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
copying django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/cs
creating build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/da
creating build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
copying django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
copying django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/da/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/de
creating build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
copying django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
copying django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/de/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/dsb
creating build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/el
creating build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
copying django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
copying django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/el/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/en
creating build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
copying django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
copying django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/en_AU
creating build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES
copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES
copying django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/eo
creating build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es
creating build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
copying django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
copying django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es_AR
creating build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es_CO
creating build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/es_MX
creating build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/et
creating build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
copying django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
copying django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/et/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/eu
creating build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/fa
creating build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/fi
creating build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/fr
creating build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/gd
creating build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/gl
creating build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/he
creating build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
copying django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
copying django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/he/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hr
creating build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hsb
creating build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hu
creating build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/hy
creating build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ia
creating build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/id
creating build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
copying django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
copying django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/id/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/is
creating build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
copying django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
copying django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/is/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/it
creating build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
copying django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
copying django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/it/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ja
creating build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ka
creating build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/kk
creating build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ko
creating build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ky
creating build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/lt
creating build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/lv
creating build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/mk
creating build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ml
creating build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/mn
creating build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ms
creating build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
copying django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/nb
creating build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ne
creating build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/nl
creating build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/nn
creating build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
copying django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/pl
creating build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/pt
creating build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/pt_BR
creating build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ro
creating build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/ru
creating build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sk
creating build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sl
creating build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sq
creating build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sr
creating build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sr_Latn
creating build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/sv
creating build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/tg
creating build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/tk
creating build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/tr
creating build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/uk
creating build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/uz
creating build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/zh_Hans
creating build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/postgres/locale/zh_Hant
creating build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/postgres/templates
creating build/lib/django/contrib/postgres/templates/postgres
creating build/lib/django/contrib/postgres/templates/postgres/widgets
copying django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/lib/django/contrib/postgres/templates/postgres/widgets
creating build/lib/django/contrib/humanize/locale
creating build/lib/django/contrib/humanize/locale/af
creating build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
copying django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
copying django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/af/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ar
creating build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ar_DZ
creating build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ast
creating build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/az
creating build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
copying django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
copying django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/az/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/be
creating build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
copying django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
copying django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/be/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/bg
creating build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/bn
creating build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/br
creating build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
copying django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
copying django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/br/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/bs
creating build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ca
creating build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ckb
creating build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
copying django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/cs
creating build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/cy
creating build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/da
creating build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
copying django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
copying django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/da/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/de
creating build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
copying django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
copying django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/de/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/dsb
creating build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/el
creating build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
copying django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
copying django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/el/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/en
creating build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
copying django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
copying django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/en_AU
creating build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/en_GB
creating build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/eo
creating build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es
creating build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
copying django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
copying django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_AR
creating build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_CO
creating build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_MX
creating build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/es_VE
creating build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/et
creating build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
copying django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
copying django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/et/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/eu
creating build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fa
creating build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fi
creating build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fr
creating build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/fy
creating build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ga
creating build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/gd
creating build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/gl
creating build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/he
creating build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
copying django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
copying django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/he/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hi
creating build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hr
creating build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hsb
creating build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hu
creating build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/hy
creating build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ia
creating build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/id
creating build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
copying django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
copying django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/id/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/io
creating build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
copying django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
copying django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/io/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/is
creating build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
copying django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
copying django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/is/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/it
creating build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
copying django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
copying django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/it/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ja
creating build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ka
creating build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/kk
creating build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/km
creating build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
copying django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
copying django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/km/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/kn
creating build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ko
creating build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ky
creating build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/lb
creating build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/lt
creating build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/lv
creating build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/mk
creating build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ml
creating build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/mn
creating build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/mr
creating build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ms
creating build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/my
creating build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
copying django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
copying django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/my/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/nb
creating build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ne
creating build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/nl
creating build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/nn
creating build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/os
creating build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
copying django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
copying django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/os/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pa
creating build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pl
creating build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pt
creating build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/pt_BR
creating build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ro
creating build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ru
creating build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sk
creating build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sl
creating build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sq
creating build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sr
creating build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sr_Latn
creating build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sv
creating build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/sw
creating build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ta
creating build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/te
creating build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
copying django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
copying django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/te/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/tg
creating build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/th
creating build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
copying django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
copying django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/th/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/tk
creating build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
copying django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/tr
creating build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/tt
creating build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/udm
creating build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/uk
creating build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/ur
creating build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/uz
creating build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/vi
creating build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/zh_Hans
creating build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/humanize/locale/zh_Hant
creating build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/gis/locale
creating build/lib/django/contrib/gis/locale/af
creating build/lib/django/contrib/gis/locale/af/LC_MESSAGES
copying django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
copying django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/af/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ar
creating build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
copying django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
copying django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ar_DZ
creating build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ast
creating build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
copying django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
copying django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/az
creating build/lib/django/contrib/gis/locale/az/LC_MESSAGES
copying django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
copying django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/az/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/be
creating build/lib/django/contrib/gis/locale/be/LC_MESSAGES
copying django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
copying django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/be/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/bg
creating build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
copying django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
copying django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/bn
creating build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
copying django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
copying django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/br
creating build/lib/django/contrib/gis/locale/br/LC_MESSAGES
copying django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
copying django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/br/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/bs
creating build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
copying django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
copying django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ca
creating build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
copying django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
copying django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ckb
creating build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
copying django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/cs
creating build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
copying django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
copying django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/cy
creating build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
copying django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
copying django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/da
creating build/lib/django/contrib/gis/locale/da/LC_MESSAGES
copying django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
copying django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/da/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/de
creating build/lib/django/contrib/gis/locale/de/LC_MESSAGES
copying django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
copying django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/de/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/dsb
creating build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/el
creating build/lib/django/contrib/gis/locale/el/LC_MESSAGES
copying django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
copying django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/el/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/en
creating build/lib/django/contrib/gis/locale/en/LC_MESSAGES
copying django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
copying django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/en_AU
creating build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/en_GB
creating build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/eo
creating build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
copying django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
copying django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es
creating build/lib/django/contrib/gis/locale/es/LC_MESSAGES
copying django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
copying django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_AR
creating build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_CO
creating build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_MX
creating build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/es_VE
creating build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/et
creating build/lib/django/contrib/gis/locale/et/LC_MESSAGES
copying django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
copying django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/et/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/eu
creating build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
copying django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
copying django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fa
creating build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
copying django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
copying django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fi
creating build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
copying django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
copying django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fr
creating build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
copying django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
copying django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/fy
creating build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
copying django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
copying django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ga
creating build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
copying django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
copying django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/gd
creating build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
copying django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
copying django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/gl
creating build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
copying django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
copying django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/he
creating build/lib/django/contrib/gis/locale/he/LC_MESSAGES
copying django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
copying django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/he/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hi
creating build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
copying django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
copying django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hr
creating build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
copying django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
copying django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hsb
creating build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hu
creating build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
copying django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
copying django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/hy
creating build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
copying django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
copying django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ia
creating build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
copying django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
copying django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/id
creating build/lib/django/contrib/gis/locale/id/LC_MESSAGES
copying django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
copying django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/id/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/io
creating build/lib/django/contrib/gis/locale/io/LC_MESSAGES
copying django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
copying django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/io/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/is
creating build/lib/django/contrib/gis/locale/is/LC_MESSAGES
copying django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
copying django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/is/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/it
creating build/lib/django/contrib/gis/locale/it/LC_MESSAGES
copying django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
copying django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/it/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ja
creating build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
copying django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
copying django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ka
creating build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
copying django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
copying django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/kk
creating build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
copying django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
copying django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/km
creating build/lib/django/contrib/gis/locale/km/LC_MESSAGES
copying django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
copying django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/km/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/kn
creating build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
copying django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
copying django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ko
creating build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
copying django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
copying django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ky
creating build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
copying django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
copying django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/lb
creating build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
copying django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
copying django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/lt
creating build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
copying django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
copying django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/lv
creating build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
copying django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
copying django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/mk
creating build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
copying django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
copying django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ml
creating build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
copying django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
copying django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/mn
creating build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
copying django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
copying django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/mr
creating build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
copying django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
copying django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ms
creating build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
copying django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
copying django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/my
creating build/lib/django/contrib/gis/locale/my/LC_MESSAGES
copying django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
copying django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/my/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/nb
creating build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
copying django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
copying django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ne
creating build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
copying django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
copying django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/nl
creating build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
copying django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
copying django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/nn
creating build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
copying django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
copying django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/os
creating build/lib/django/contrib/gis/locale/os/LC_MESSAGES
copying django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
copying django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/os/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pa
creating build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
copying django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
copying django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pl
creating build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
copying django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
copying django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pt
creating build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
copying django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
copying django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/pt_BR
creating build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ro
creating build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
copying django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
copying django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ru
creating build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
copying django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
copying django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sk
creating build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
copying django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
copying django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sl
creating build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
copying django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
copying django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sq
creating build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
copying django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
copying django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sr
creating build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
copying django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
copying django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sr_Latn
creating build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sv
creating build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
copying django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
copying django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/sw
creating build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
copying django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
copying django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ta
creating build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
copying django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
copying django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/te
creating build/lib/django/contrib/gis/locale/te/LC_MESSAGES
copying django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
copying django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/te/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/tg
creating build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
copying django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
copying django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/th
creating build/lib/django/contrib/gis/locale/th/LC_MESSAGES
copying django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
copying django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/th/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/tr
creating build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
copying django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
copying django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/tt
creating build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
copying django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
copying django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/udm
creating build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
copying django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
copying django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/uk
creating build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
copying django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
copying django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/ur
creating build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
copying django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
copying django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/vi
creating build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
copying django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
copying django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/zh_Hans
creating build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/gis/locale/zh_Hant
creating build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/gis/static
creating build/lib/django/contrib/gis/static/gis
creating build/lib/django/contrib/gis/static/gis/css
copying django/contrib/gis/static/gis/css/ol3.css -> build/lib/django/contrib/gis/static/gis/css
creating build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_line_off.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_line_on.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_point_off.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_point_on.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/lib/django/contrib/gis/static/gis/img
copying django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/lib/django/contrib/gis/static/gis/img
creating build/lib/django/contrib/gis/static/gis/js
copying django/contrib/gis/static/gis/js/OLMapWidget.js -> build/lib/django/contrib/gis/static/gis/js
creating build/lib/django/contrib/gis/templates
creating build/lib/django/contrib/gis/templates/gis
copying django/contrib/gis/templates/gis/openlayers-osm.html -> build/lib/django/contrib/gis/templates/gis
copying django/contrib/gis/templates/gis/openlayers.html -> build/lib/django/contrib/gis/templates/gis
creating build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/openlayers.html -> build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/openlayers.js -> build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/osm.html -> build/lib/django/contrib/gis/templates/gis/admin
copying django/contrib/gis/templates/gis/admin/osm.js -> build/lib/django/contrib/gis/templates/gis/admin
creating build/lib/django/contrib/gis/templates/gis/kml
copying django/contrib/gis/templates/gis/kml/base.kml -> build/lib/django/contrib/gis/templates/gis/kml
copying django/contrib/gis/templates/gis/kml/placemarks.kml -> build/lib/django/contrib/gis/templates/gis/kml
creating build/lib/django/contrib/flatpages/locale
creating build/lib/django/contrib/flatpages/locale/af
creating build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ar
creating build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ar_DZ
creating build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ast
creating build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/az
creating build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/be
creating build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/bg
creating build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/bn
creating build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/br
creating build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/bs
creating build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ca
creating build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ckb
creating build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
copying django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/cs
creating build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/cy
creating build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/da
creating build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/de
creating build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/dsb
creating build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/el
creating build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/en
creating build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/en_AU
creating build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/en_GB
creating build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/eo
creating build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es
creating build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_AR
creating build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_CO
creating build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_MX
creating build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/es_VE
creating build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/et
creating build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/eu
creating build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fa
creating build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fi
creating build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fr
creating build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/fy
creating build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ga
creating build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/gd
creating build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/gl
creating build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/he
creating build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hi
creating build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hr
creating build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hsb
creating build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hu
creating build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/hy
creating build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ia
creating build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/id
creating build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/io
creating build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/is
creating build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/it
creating build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ja
creating build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ka
creating build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/kk
creating build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/km
creating build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/kn
creating build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ko
creating build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ky
creating build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/lb
creating build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/lt
creating build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/lv
creating build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/mk
creating build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ml
creating build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/mn
creating build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/mr
creating build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ms
creating build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
copying django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/my
creating build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/nb
creating build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ne
creating build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/nl
creating build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/nn
creating build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/os
creating build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pa
creating build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pl
creating build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pt
creating build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/pt_BR
creating build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ro
creating build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ru
creating build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sk
creating build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sl
creating build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sq
creating build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sr
creating build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sr_Latn
creating build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sv
creating build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/sw
creating build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ta
creating build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/te
creating build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tg
creating build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/th
creating build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tk
creating build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tr
creating build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/tt
creating build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/udm
creating build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/uk
creating build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/ur
creating build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/vi
creating build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/zh_Hans
creating build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/flatpages/locale/zh_Hant
creating build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale
creating build/lib/django/contrib/contenttypes/locale/af
creating build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ar
creating build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ar_DZ
creating build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ast
creating build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/az
creating build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/be
creating build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/bg
creating build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/bn
creating build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/br
creating build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/bs
creating build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ca
creating build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ckb
creating build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
copying django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/cs
creating build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/cy
creating build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/da
creating build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/de
creating build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/dsb
creating build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/el
creating build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/en
creating build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/en_AU
creating build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/en_GB
creating build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/eo
creating build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es
creating build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_AR
creating build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_CO
creating build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_MX
creating build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/es_VE
creating build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/et
creating build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/eu
creating build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fa
creating build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fi
creating build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fr
creating build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/fy
creating build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ga
creating build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/gd
creating build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/gl
creating build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/he
creating build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hi
creating build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hr
creating build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hsb
creating build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hu
creating build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/hy
creating build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ia
creating build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/id
creating build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/io
creating build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/is
creating build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/it
creating build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ja
creating build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ka
creating build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/kk
creating build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/km
creating build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/kn
creating build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ko
creating build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ky
creating build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/lb
creating build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/lt
creating build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/lv
creating build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/mk
creating build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ml
creating build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/mn
creating build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/mr
creating build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ms
creating build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
copying django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/my
creating build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/nb
creating build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ne
creating build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/nl
creating build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/nn
creating build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/os
creating build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pa
creating build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pl
creating build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pt
creating build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/pt_BR
creating build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ro
creating build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ru
creating build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sk
creating build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sl
creating build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sq
creating build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sr
creating build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sr_Latn
creating build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sv
creating build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/sw
creating build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ta
creating build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/te
creating build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tg
creating build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/th
creating build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tk
creating build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tr
creating build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/tt
creating build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/udm
creating build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/uk
creating build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/ur
creating build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/vi
creating build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/zh_Hans
creating build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/contenttypes/locale/zh_Hant
creating build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying django/contrib/auth/common-passwords.txt.gz -> build/lib/django/contrib/auth
creating build/lib/django/contrib/auth/locale
creating build/lib/django/contrib/auth/locale/af
creating build/lib/django/contrib/auth/locale/af/LC_MESSAGES
copying django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
copying django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/af/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ar
creating build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
copying django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
copying django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ar_DZ
creating build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ast
creating build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
copying django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
copying django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/az
creating build/lib/django/contrib/auth/locale/az/LC_MESSAGES
copying django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
copying django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/az/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/be
creating build/lib/django/contrib/auth/locale/be/LC_MESSAGES
copying django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
copying django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/be/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/bg
creating build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
copying django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
copying django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/bn
creating build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
copying django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
copying django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/br
creating build/lib/django/contrib/auth/locale/br/LC_MESSAGES
copying django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
copying django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/br/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/bs
creating build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
copying django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
copying django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ca
creating build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
copying django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
copying django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ckb
creating build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
copying django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/cs
creating build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
copying django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
copying django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/cy
creating build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
copying django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
copying django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/da
creating build/lib/django/contrib/auth/locale/da/LC_MESSAGES
copying django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
copying django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/da/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/de
creating build/lib/django/contrib/auth/locale/de/LC_MESSAGES
copying django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
copying django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/de/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/dsb
creating build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/el
creating build/lib/django/contrib/auth/locale/el/LC_MESSAGES
copying django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
copying django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/el/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/en
creating build/lib/django/contrib/auth/locale/en/LC_MESSAGES
copying django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
copying django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/en_AU
creating build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/en_GB
creating build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/eo
creating build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
copying django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
copying django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es
creating build/lib/django/contrib/auth/locale/es/LC_MESSAGES
copying django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
copying django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_AR
creating build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_CO
creating build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_MX
creating build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/es_VE
creating build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/et
creating build/lib/django/contrib/auth/locale/et/LC_MESSAGES
copying django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
copying django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/et/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/eu
creating build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
copying django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
copying django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fa
creating build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
copying django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
copying django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fi
creating build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
copying django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
copying django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fr
creating build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
copying django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
copying django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/fy
creating build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
copying django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
copying django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ga
creating build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
copying django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
copying django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/gd
creating build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
copying django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
copying django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/gl
creating build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
copying django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
copying django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/he
creating build/lib/django/contrib/auth/locale/he/LC_MESSAGES
copying django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
copying django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/he/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hi
creating build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
copying django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
copying django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hr
creating build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
copying django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
copying django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hsb
creating build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hu
creating build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
copying django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
copying django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/hy
creating build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
copying django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
copying django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ia
creating build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
copying django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
copying django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/id
creating build/lib/django/contrib/auth/locale/id/LC_MESSAGES
copying django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
copying django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/id/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/io
creating build/lib/django/contrib/auth/locale/io/LC_MESSAGES
copying django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
copying django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/io/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/is
creating build/lib/django/contrib/auth/locale/is/LC_MESSAGES
copying django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
copying django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/is/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/it
creating build/lib/django/contrib/auth/locale/it/LC_MESSAGES
copying django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
copying django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/it/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ja
creating build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
copying django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
copying django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ka
creating build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
copying django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
copying django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/kab
creating build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
copying django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
copying django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/kk
creating build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
copying django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
copying django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/km
creating build/lib/django/contrib/auth/locale/km/LC_MESSAGES
copying django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
copying django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/km/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/kn
creating build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
copying django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
copying django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ko
creating build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
copying django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
copying django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ky
creating build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
copying django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
copying django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/lb
creating build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
copying django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
copying django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/lt
creating build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
copying django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
copying django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/lv
creating build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
copying django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
copying django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/mk
creating build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
copying django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
copying django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ml
creating build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
copying django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
copying django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/mn
creating build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
copying django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
copying django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/mr
creating build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
copying django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
copying django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ms
creating build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
copying django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
copying django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/my
creating build/lib/django/contrib/auth/locale/my/LC_MESSAGES
copying django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
copying django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/my/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/nb
creating build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
copying django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
copying django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ne
creating build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
copying django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
copying django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/nl
creating build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
copying django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
copying django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/nn
creating build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
copying django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
copying django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/os
creating build/lib/django/contrib/auth/locale/os/LC_MESSAGES
copying django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
copying django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/os/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pa
creating build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
copying django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
copying django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pl
creating build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
copying django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
copying django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pt
creating build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
copying django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
copying django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/pt_BR
creating build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ro
creating build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
copying django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
copying django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ru
creating build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
copying django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
copying django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sk
creating build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
copying django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
copying django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sl
creating build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
copying django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
copying django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sq
creating build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
copying django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
copying django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sr
creating build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
copying django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
copying django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sr_Latn
creating build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sv
creating build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
copying django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
copying django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/sw
creating build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
copying django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
copying django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ta
creating build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
copying django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
copying django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/te
creating build/lib/django/contrib/auth/locale/te/LC_MESSAGES
copying django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
copying django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/te/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tg
creating build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
copying django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
copying django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/th
creating build/lib/django/contrib/auth/locale/th/LC_MESSAGES
copying django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
copying django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/th/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tk
creating build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
copying django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
copying django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tr
creating build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
copying django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
copying django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/tt
creating build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
copying django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
copying django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/udm
creating build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
copying django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
copying django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/uk
creating build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
copying django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
copying django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/ur
creating build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
copying django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
copying django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/uz
creating build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
copying django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
copying django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/vi
creating build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
copying django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
copying django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/zh_Hans
creating build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/auth/locale/zh_Hant
creating build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/auth/templates
creating build/lib/django/contrib/auth/templates/auth
creating build/lib/django/contrib/auth/templates/auth/widgets
copying django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/lib/django/contrib/auth/templates/auth/widgets
creating build/lib/django/contrib/auth/templates/registration
copying django/contrib/auth/templates/registration/password_reset_subject.txt -> build/lib/django/contrib/auth/templates/registration
creating build/lib/django/contrib/admindocs/locale
creating build/lib/django/contrib/admindocs/locale/af
creating build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ar
creating build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ar_DZ
creating build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ast
creating build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/az
creating build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/be
creating build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/bg
creating build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/bn
creating build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/br
creating build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/bs
creating build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ca
creating build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ckb
creating build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
copying django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/cs
creating build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/cy
creating build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/da
creating build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/de
creating build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/dsb
creating build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/el
creating build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/en
creating build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/en_AU
creating build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/en_GB
creating build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/eo
creating build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es
creating build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_AR
creating build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_CO
creating build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_MX
creating build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/es_VE
creating build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/et
creating build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/eu
creating build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fa
creating build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fi
creating build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fr
creating build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/fy
creating build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ga
creating build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/gd
creating build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/gl
creating build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/he
creating build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hi
creating build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hr
creating build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hsb
creating build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/hu
creating build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ia
creating build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/id
creating build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/io
creating build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/is
creating build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/it
creating build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ja
creating build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ka
creating build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/kab
creating build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/kk
creating build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/km
creating build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/kn
creating build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ko
creating build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ky
creating build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/lb
creating build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/lt
creating build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/lv
creating build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/mk
creating build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ml
creating build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/mn
creating build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/mr
creating build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ms
creating build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
copying django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/my
creating build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/nb
creating build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ne
creating build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/nl
creating build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/nn
creating build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/os
creating build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pa
creating build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pl
creating build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pt
creating build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/pt_BR
creating build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ro
creating build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ru
creating build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sk
creating build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sl
creating build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sq
creating build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sr
creating build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sr_Latn
creating build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sv
creating build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/sw
creating build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ta
creating build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/te
creating build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/tg
creating build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/th
creating build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/tr
creating build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/tt
creating build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/udm
creating build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/uk
creating build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/ur
creating build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/vi
creating build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/zh_Hans
creating build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/admindocs/locale/zh_Hant
creating build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/admindocs/templates
creating build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/model_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/lib/django/contrib/admindocs/templates/admin_doc
copying django/contrib/admindocs/templates/admin_doc/view_index.html -> build/lib/django/contrib/admindocs/templates/admin_doc
creating build/lib/django/contrib/admin/locale
creating build/lib/django/contrib/admin/locale/af
creating build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/af/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/am
creating build/lib/django/contrib/admin/locale/am/LC_MESSAGES
copying django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
copying django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/am/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ar
creating build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ar_DZ
creating build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ast
creating build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ast/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/az
creating build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/az/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/be
creating build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/be/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/bg
creating build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bg/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/bn
creating build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/br
creating build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/br/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/bs
creating build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/bs/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ca
creating build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ca/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ckb
creating build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
copying django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
copying django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/cs
creating build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cs/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/cy
creating build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/cy/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/da
creating build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/da/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/de
creating build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/de/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/dsb
creating build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/el
creating build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/el/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/en
creating build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/en_AU
creating build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/en_GB
creating build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/eo
creating build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eo/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es
creating build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_AR
creating build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_CO
creating build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_MX
creating build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/es_VE
creating build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/et
creating build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/et/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/eu
creating build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/eu/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fa
creating build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fa/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fi
creating build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fi/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fr
creating build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/fy
creating build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/fy/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ga
creating build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ga/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/gd
creating build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gd/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/gl
creating build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/gl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/he
creating build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/he/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hi
creating build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hi/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hr
creating build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hsb
creating build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hu
creating build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hu/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/hy
creating build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/hy/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ia
creating build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ia/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/id
creating build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/id/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/io
creating build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/io/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/is
creating build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/is/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/it
creating build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/it/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ja
creating build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ja/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ka
creating build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ka/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/kab
creating build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kab/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/kk
creating build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/km
creating build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/km/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/kn
creating build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/kn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ko
creating build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ko/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ky
creating build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ky/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/lb
creating build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/lt
creating build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lt/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/lv
creating build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/lv/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/mk
creating build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ml
creating build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ml/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/mn
creating build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/mr
creating build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/mr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ms
creating build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
copying django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
copying django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
copying django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ms/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/my
creating build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/my/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/nb
creating build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nb/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ne
creating build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ne/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/nl
creating build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/nn
creating build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/nn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/os
creating build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/os/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pa
creating build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pa/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pl
creating build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pt
creating build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/pt_BR
creating build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ro
creating build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ro/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ru
creating build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ru/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sk
creating build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sl
creating build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sl/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sq
creating build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sq/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sr
creating build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sr_Latn
creating build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sv
creating build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sv/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/sw
creating build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/sw/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ta
creating build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ta/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/te
creating build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/te/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/tg
creating build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tg/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/th
creating build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/th/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/tk
creating build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
copying django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
copying django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/tr
creating build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tr/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/tt
creating build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/tt/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/udm
creating build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/udm/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/uk
creating build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uk/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/ur
creating build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/ur/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/uz
creating build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/uz/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/vi
creating build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/vi/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/zh_Hans
creating build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/contrib/admin/locale/zh_Hant
creating build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/contrib/admin/static
creating build/lib/django/contrib/admin/static/admin
creating build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/autocomplete.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/base.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/changelists.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/dark_mode.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/dashboard.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/forms.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/login.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/nav_sidebar.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/responsive.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/responsive_rtl.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/rtl.css -> build/lib/django/contrib/admin/static/admin/css
copying django/contrib/admin/static/admin/css/widgets.css -> build/lib/django/contrib/admin/static/admin/css
creating build/lib/django/contrib/admin/static/admin/css/vendor
creating build/lib/django/contrib/admin/static/admin/css/vendor/select2
copying django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
copying django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
copying django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/lib/django/contrib/admin/static/admin/css/vendor/select2
creating build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/LICENSE -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/README.txt -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/calendar-icons.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-addlink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-alert.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-calendar.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-changelink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-clock.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-no.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-unknown.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/icon-yes.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/inline-delete.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/search.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/selector-icons.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/sorting-icons.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/tooltag-add.svg -> build/lib/django/contrib/admin/static/admin/img
copying django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/lib/django/contrib/admin/static/admin/img
creating build/lib/django/contrib/admin/static/admin/img/gis
copying django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/lib/django/contrib/admin/static/admin/img/gis
copying django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/lib/django/contrib/admin/static/admin/img/gis
creating build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/SelectBox.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/SelectFilter2.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/actions.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/autocomplete.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/calendar.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/cancel.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/change_form.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/collapse.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/core.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/filters.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/inlines.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/jquery.init.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/nav_sidebar.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/popup_response.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/prepopulate.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/prepopulate_init.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/theme.js -> build/lib/django/contrib/admin/static/admin/js
copying django/contrib/admin/static/admin/js/urlify.js -> build/lib/django/contrib/admin/static/admin/js
creating build/lib/django/contrib/admin/static/admin/js/admin
copying django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/lib/django/contrib/admin/static/admin/js/admin
copying django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/lib/django/contrib/admin/static/admin/js/admin
creating build/lib/django/contrib/admin/static/admin/js/vendor
creating build/lib/django/contrib/admin/static/admin/js/vendor/jquery
copying django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/jquery
creating build/lib/django/contrib/admin/static/admin/js/vendor/select2
copying django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2
creating build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n
creating build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
copying django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/lib/django/contrib/admin/static/admin/js/vendor/xregexp
creating build/lib/django/contrib/admin/templates
creating build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/404.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/500.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/actions.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/app_index.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/app_list.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/base.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/base_site.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_form.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_form_object_tools.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_list.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_list_object_tools.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/change_list_results.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/color_theme_toggle.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/date_hierarchy.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/delete_confirmation.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/filter.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/index.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/invalid_setup.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/login.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/nav_sidebar.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/object_history.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/pagination.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/popup_response.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/search_form.html -> build/lib/django/contrib/admin/templates/admin
copying django/contrib/admin/templates/admin/submit_line.html -> build/lib/django/contrib/admin/templates/admin
creating build/lib/django/contrib/admin/templates/admin/auth
creating build/lib/django/contrib/admin/templates/admin/auth/user
copying django/contrib/admin/templates/admin/auth/user/add_form.html -> build/lib/django/contrib/admin/templates/admin/auth/user
copying django/contrib/admin/templates/admin/auth/user/change_password.html -> build/lib/django/contrib/admin/templates/admin/auth/user
creating build/lib/django/contrib/admin/templates/admin/edit_inline
copying django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
copying django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/lib/django/contrib/admin/templates/admin/edit_inline
creating build/lib/django/contrib/admin/templates/admin/includes
copying django/contrib/admin/templates/admin/includes/fieldset.html -> build/lib/django/contrib/admin/templates/admin/includes
copying django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/lib/django/contrib/admin/templates/admin/includes
creating build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/date.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/radio.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/time.html -> build/lib/django/contrib/admin/templates/admin/widgets
copying django/contrib/admin/templates/admin/widgets/url.html -> build/lib/django/contrib/admin/templates/admin/widgets
creating build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/logged_out.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_change_done.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_change_form.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_complete.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_confirm.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_done.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_email.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/admin/templates/registration/password_reset_form.html -> build/lib/django/contrib/admin/templates/registration
copying django/contrib/gis/geos/LICENSE -> build/lib/django/contrib/gis/geos
copying django/contrib/gis/gdal/LICENSE -> build/lib/django/contrib/gis/gdal
creating build/lib/django/conf/locale/af
creating build/lib/django/conf/locale/af/LC_MESSAGES
copying django/conf/locale/af/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/af/LC_MESSAGES
copying django/conf/locale/af/LC_MESSAGES/django.po -> build/lib/django/conf/locale/af/LC_MESSAGES
creating build/lib/django/conf/locale/ast
creating build/lib/django/conf/locale/ast/LC_MESSAGES
copying django/conf/locale/ast/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ast/LC_MESSAGES
copying django/conf/locale/ast/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ast/LC_MESSAGES
creating build/lib/django/conf/locale/be
creating build/lib/django/conf/locale/be/LC_MESSAGES
copying django/conf/locale/be/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/be/LC_MESSAGES
copying django/conf/locale/be/LC_MESSAGES/django.po -> build/lib/django/conf/locale/be/LC_MESSAGES
creating build/lib/django/conf/locale/br
creating build/lib/django/conf/locale/br/LC_MESSAGES
copying django/conf/locale/br/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/br/LC_MESSAGES
copying django/conf/locale/br/LC_MESSAGES/django.po -> build/lib/django/conf/locale/br/LC_MESSAGES
creating build/lib/django/conf/locale/dsb
creating build/lib/django/conf/locale/dsb/LC_MESSAGES
copying django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/dsb/LC_MESSAGES
copying django/conf/locale/dsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/dsb/LC_MESSAGES
creating build/lib/django/conf/locale/es_VE
creating build/lib/django/conf/locale/es_VE/LC_MESSAGES
copying django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
copying django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_VE/LC_MESSAGES
creating build/lib/django/conf/locale/hsb
creating build/lib/django/conf/locale/hsb/LC_MESSAGES
copying django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hsb/LC_MESSAGES
copying django/conf/locale/hsb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hsb/LC_MESSAGES
creating build/lib/django/conf/locale/hy
creating build/lib/django/conf/locale/hy/LC_MESSAGES
copying django/conf/locale/hy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hy/LC_MESSAGES
copying django/conf/locale/hy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hy/LC_MESSAGES
creating build/lib/django/conf/locale/ia
creating build/lib/django/conf/locale/ia/LC_MESSAGES
copying django/conf/locale/ia/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ia/LC_MESSAGES
copying django/conf/locale/ia/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ia/LC_MESSAGES
creating build/lib/django/conf/locale/io
creating build/lib/django/conf/locale/io/LC_MESSAGES
copying django/conf/locale/io/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/io/LC_MESSAGES
copying django/conf/locale/io/LC_MESSAGES/django.po -> build/lib/django/conf/locale/io/LC_MESSAGES
creating build/lib/django/conf/locale/kab
creating build/lib/django/conf/locale/kab/LC_MESSAGES
copying django/conf/locale/kab/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kab/LC_MESSAGES
copying django/conf/locale/kab/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kab/LC_MESSAGES
creating build/lib/django/conf/locale/kk
creating build/lib/django/conf/locale/kk/LC_MESSAGES
copying django/conf/locale/kk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kk/LC_MESSAGES
copying django/conf/locale/kk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kk/LC_MESSAGES
creating build/lib/django/conf/locale/lb
creating build/lib/django/conf/locale/lb/LC_MESSAGES
copying django/conf/locale/lb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lb/LC_MESSAGES
copying django/conf/locale/lb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lb/LC_MESSAGES
creating build/lib/django/conf/locale/mr
creating build/lib/django/conf/locale/mr/LC_MESSAGES
copying django/conf/locale/mr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mr/LC_MESSAGES
copying django/conf/locale/mr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mr/LC_MESSAGES
creating build/lib/django/conf/locale/my
creating build/lib/django/conf/locale/my/LC_MESSAGES
copying django/conf/locale/my/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/my/LC_MESSAGES
copying django/conf/locale/my/LC_MESSAGES/django.po -> build/lib/django/conf/locale/my/LC_MESSAGES
creating build/lib/django/conf/locale/ne
creating build/lib/django/conf/locale/ne/LC_MESSAGES
copying django/conf/locale/ne/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ne/LC_MESSAGES
copying django/conf/locale/ne/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ne/LC_MESSAGES
creating build/lib/django/conf/locale/os
creating build/lib/django/conf/locale/os/LC_MESSAGES
copying django/conf/locale/os/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/os/LC_MESSAGES
copying django/conf/locale/os/LC_MESSAGES/django.po -> build/lib/django/conf/locale/os/LC_MESSAGES
creating build/lib/django/conf/locale/pa
creating build/lib/django/conf/locale/pa/LC_MESSAGES
copying django/conf/locale/pa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pa/LC_MESSAGES
copying django/conf/locale/pa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pa/LC_MESSAGES
creating build/lib/django/conf/locale/sw
creating build/lib/django/conf/locale/sw/LC_MESSAGES
copying django/conf/locale/sw/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sw/LC_MESSAGES
copying django/conf/locale/sw/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sw/LC_MESSAGES
creating build/lib/django/conf/locale/tt
creating build/lib/django/conf/locale/tt/LC_MESSAGES
copying django/conf/locale/tt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tt/LC_MESSAGES
copying django/conf/locale/tt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tt/LC_MESSAGES
creating build/lib/django/conf/locale/udm
creating build/lib/django/conf/locale/udm/LC_MESSAGES
copying django/conf/locale/udm/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/udm/LC_MESSAGES
copying django/conf/locale/udm/LC_MESSAGES/django.po -> build/lib/django/conf/locale/udm/LC_MESSAGES
creating build/lib/django/conf/locale/ur
creating build/lib/django/conf/locale/ur/LC_MESSAGES
copying django/conf/locale/ur/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ur/LC_MESSAGES
copying django/conf/locale/ur/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ur/LC_MESSAGES
creating build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
copying django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
copying django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hant/LC_MESSAGES
creating build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
copying django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
copying django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django/conf/locale/zh_Hans/LC_MESSAGES
creating build/lib/django/conf/locale/vi/LC_MESSAGES
copying django/conf/locale/vi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/vi/LC_MESSAGES
copying django/conf/locale/vi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/vi/LC_MESSAGES
creating build/lib/django/conf/locale/uz/LC_MESSAGES
copying django/conf/locale/uz/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uz/LC_MESSAGES
copying django/conf/locale/uz/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uz/LC_MESSAGES
creating build/lib/django/conf/locale/uk/LC_MESSAGES
copying django/conf/locale/uk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/uk/LC_MESSAGES
copying django/conf/locale/uk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/uk/LC_MESSAGES
creating build/lib/django/conf/locale/tr/LC_MESSAGES
copying django/conf/locale/tr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tr/LC_MESSAGES
copying django/conf/locale/tr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tr/LC_MESSAGES
creating build/lib/django/conf/locale/tk/LC_MESSAGES
copying django/conf/locale/tk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tk/LC_MESSAGES
copying django/conf/locale/tk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tk/LC_MESSAGES
creating build/lib/django/conf/locale/th/LC_MESSAGES
copying django/conf/locale/th/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/th/LC_MESSAGES
copying django/conf/locale/th/LC_MESSAGES/django.po -> build/lib/django/conf/locale/th/LC_MESSAGES
creating build/lib/django/conf/locale/tg/LC_MESSAGES
copying django/conf/locale/tg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/tg/LC_MESSAGES
copying django/conf/locale/tg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/tg/LC_MESSAGES
creating build/lib/django/conf/locale/te/LC_MESSAGES
copying django/conf/locale/te/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/te/LC_MESSAGES
copying django/conf/locale/te/LC_MESSAGES/django.po -> build/lib/django/conf/locale/te/LC_MESSAGES
creating build/lib/django/conf/locale/ta/LC_MESSAGES
copying django/conf/locale/ta/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ta/LC_MESSAGES
copying django/conf/locale/ta/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ta/LC_MESSAGES
creating build/lib/django/conf/locale/sv/LC_MESSAGES
copying django/conf/locale/sv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sv/LC_MESSAGES
copying django/conf/locale/sv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sv/LC_MESSAGES
creating build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
copying django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
copying django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr_Latn/LC_MESSAGES
creating build/lib/django/conf/locale/sr/LC_MESSAGES
copying django/conf/locale/sr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sr/LC_MESSAGES
copying django/conf/locale/sr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sr/LC_MESSAGES
creating build/lib/django/conf/locale/sq/LC_MESSAGES
copying django/conf/locale/sq/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sq/LC_MESSAGES
copying django/conf/locale/sq/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sq/LC_MESSAGES
creating build/lib/django/conf/locale/sl/LC_MESSAGES
copying django/conf/locale/sl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sl/LC_MESSAGES
copying django/conf/locale/sl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sl/LC_MESSAGES
creating build/lib/django/conf/locale/sk/LC_MESSAGES
copying django/conf/locale/sk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/sk/LC_MESSAGES
copying django/conf/locale/sk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/sk/LC_MESSAGES
creating build/lib/django/conf/locale/ru/LC_MESSAGES
copying django/conf/locale/ru/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ru/LC_MESSAGES
copying django/conf/locale/ru/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ru/LC_MESSAGES
creating build/lib/django/conf/locale/ro/LC_MESSAGES
copying django/conf/locale/ro/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ro/LC_MESSAGES
copying django/conf/locale/ro/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ro/LC_MESSAGES
creating build/lib/django/conf/locale/pt_BR/LC_MESSAGES
copying django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
copying django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt_BR/LC_MESSAGES
creating build/lib/django/conf/locale/pt/LC_MESSAGES
copying django/conf/locale/pt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pt/LC_MESSAGES
copying django/conf/locale/pt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pt/LC_MESSAGES
creating build/lib/django/conf/locale/pl/LC_MESSAGES
copying django/conf/locale/pl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/pl/LC_MESSAGES
copying django/conf/locale/pl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/pl/LC_MESSAGES
creating build/lib/django/conf/locale/nn/LC_MESSAGES
copying django/conf/locale/nn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nn/LC_MESSAGES
copying django/conf/locale/nn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nn/LC_MESSAGES
creating build/lib/django/conf/locale/nl/LC_MESSAGES
copying django/conf/locale/nl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nl/LC_MESSAGES
copying django/conf/locale/nl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nl/LC_MESSAGES
creating build/lib/django/conf/locale/nb/LC_MESSAGES
copying django/conf/locale/nb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/nb/LC_MESSAGES
copying django/conf/locale/nb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/nb/LC_MESSAGES
creating build/lib/django/conf/locale/ms/LC_MESSAGES
copying django/conf/locale/ms/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ms/LC_MESSAGES
copying django/conf/locale/ms/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ms/LC_MESSAGES
creating build/lib/django/conf/locale/mn/LC_MESSAGES
copying django/conf/locale/mn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mn/LC_MESSAGES
copying django/conf/locale/mn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mn/LC_MESSAGES
creating build/lib/django/conf/locale/ml/LC_MESSAGES
copying django/conf/locale/ml/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ml/LC_MESSAGES
copying django/conf/locale/ml/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ml/LC_MESSAGES
creating build/lib/django/conf/locale/mk/LC_MESSAGES
copying django/conf/locale/mk/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/mk/LC_MESSAGES
copying django/conf/locale/mk/LC_MESSAGES/django.po -> build/lib/django/conf/locale/mk/LC_MESSAGES
creating build/lib/django/conf/locale/lv/LC_MESSAGES
copying django/conf/locale/lv/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lv/LC_MESSAGES
copying django/conf/locale/lv/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lv/LC_MESSAGES
creating build/lib/django/conf/locale/lt/LC_MESSAGES
copying django/conf/locale/lt/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/lt/LC_MESSAGES
copying django/conf/locale/lt/LC_MESSAGES/django.po -> build/lib/django/conf/locale/lt/LC_MESSAGES
creating build/lib/django/conf/locale/ky/LC_MESSAGES
copying django/conf/locale/ky/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ky/LC_MESSAGES
copying django/conf/locale/ky/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ky/LC_MESSAGES
creating build/lib/django/conf/locale/ko/LC_MESSAGES
copying django/conf/locale/ko/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ko/LC_MESSAGES
copying django/conf/locale/ko/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ko/LC_MESSAGES
creating build/lib/django/conf/locale/kn/LC_MESSAGES
copying django/conf/locale/kn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/kn/LC_MESSAGES
copying django/conf/locale/kn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/kn/LC_MESSAGES
creating build/lib/django/conf/locale/km/LC_MESSAGES
copying django/conf/locale/km/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/km/LC_MESSAGES
copying django/conf/locale/km/LC_MESSAGES/django.po -> build/lib/django/conf/locale/km/LC_MESSAGES
creating build/lib/django/conf/locale/ka/LC_MESSAGES
copying django/conf/locale/ka/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ka/LC_MESSAGES
copying django/conf/locale/ka/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ka/LC_MESSAGES
creating build/lib/django/conf/locale/ja/LC_MESSAGES
copying django/conf/locale/ja/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ja/LC_MESSAGES
copying django/conf/locale/ja/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ja/LC_MESSAGES
creating build/lib/django/conf/locale/it/LC_MESSAGES
copying django/conf/locale/it/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/it/LC_MESSAGES
copying django/conf/locale/it/LC_MESSAGES/django.po -> build/lib/django/conf/locale/it/LC_MESSAGES
creating build/lib/django/conf/locale/is/LC_MESSAGES
copying django/conf/locale/is/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/is/LC_MESSAGES
copying django/conf/locale/is/LC_MESSAGES/django.po -> build/lib/django/conf/locale/is/LC_MESSAGES
creating build/lib/django/conf/locale/ig/LC_MESSAGES
copying django/conf/locale/ig/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ig/LC_MESSAGES
copying django/conf/locale/ig/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ig/LC_MESSAGES
creating build/lib/django/conf/locale/id/LC_MESSAGES
copying django/conf/locale/id/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/id/LC_MESSAGES
copying django/conf/locale/id/LC_MESSAGES/django.po -> build/lib/django/conf/locale/id/LC_MESSAGES
creating build/lib/django/conf/locale/hu/LC_MESSAGES
copying django/conf/locale/hu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hu/LC_MESSAGES
copying django/conf/locale/hu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hu/LC_MESSAGES
creating build/lib/django/conf/locale/hr/LC_MESSAGES
copying django/conf/locale/hr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hr/LC_MESSAGES
copying django/conf/locale/hr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hr/LC_MESSAGES
creating build/lib/django/conf/locale/hi/LC_MESSAGES
copying django/conf/locale/hi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/hi/LC_MESSAGES
copying django/conf/locale/hi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/hi/LC_MESSAGES
creating build/lib/django/conf/locale/he/LC_MESSAGES
copying django/conf/locale/he/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/he/LC_MESSAGES
copying django/conf/locale/he/LC_MESSAGES/django.po -> build/lib/django/conf/locale/he/LC_MESSAGES
creating build/lib/django/conf/locale/gl/LC_MESSAGES
copying django/conf/locale/gl/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gl/LC_MESSAGES
copying django/conf/locale/gl/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gl/LC_MESSAGES
creating build/lib/django/conf/locale/gd/LC_MESSAGES
copying django/conf/locale/gd/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/gd/LC_MESSAGES
copying django/conf/locale/gd/LC_MESSAGES/django.po -> build/lib/django/conf/locale/gd/LC_MESSAGES
creating build/lib/django/conf/locale/ga/LC_MESSAGES
copying django/conf/locale/ga/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ga/LC_MESSAGES
copying django/conf/locale/ga/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ga/LC_MESSAGES
creating build/lib/django/conf/locale/fy/LC_MESSAGES
copying django/conf/locale/fy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fy/LC_MESSAGES
copying django/conf/locale/fy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fy/LC_MESSAGES
creating build/lib/django/conf/locale/fr/LC_MESSAGES
copying django/conf/locale/fr/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fr/LC_MESSAGES
copying django/conf/locale/fr/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fr/LC_MESSAGES
creating build/lib/django/conf/locale/fi/LC_MESSAGES
copying django/conf/locale/fi/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fi/LC_MESSAGES
copying django/conf/locale/fi/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fi/LC_MESSAGES
creating build/lib/django/conf/locale/fa/LC_MESSAGES
copying django/conf/locale/fa/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/fa/LC_MESSAGES
copying django/conf/locale/fa/LC_MESSAGES/django.po -> build/lib/django/conf/locale/fa/LC_MESSAGES
creating build/lib/django/conf/locale/eu/LC_MESSAGES
copying django/conf/locale/eu/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eu/LC_MESSAGES
copying django/conf/locale/eu/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eu/LC_MESSAGES
creating build/lib/django/conf/locale/et/LC_MESSAGES
copying django/conf/locale/et/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/et/LC_MESSAGES
copying django/conf/locale/et/LC_MESSAGES/django.po -> build/lib/django/conf/locale/et/LC_MESSAGES
creating build/lib/django/conf/locale/es_MX/LC_MESSAGES
copying django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
copying django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_MX/LC_MESSAGES
creating build/lib/django/conf/locale/es_CO/LC_MESSAGES
copying django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
copying django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_CO/LC_MESSAGES
creating build/lib/django/conf/locale/es_AR/LC_MESSAGES
copying django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
copying django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es_AR/LC_MESSAGES
creating build/lib/django/conf/locale/es/LC_MESSAGES
copying django/conf/locale/es/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/es/LC_MESSAGES
copying django/conf/locale/es/LC_MESSAGES/django.po -> build/lib/django/conf/locale/es/LC_MESSAGES
creating build/lib/django/conf/locale/eo/LC_MESSAGES
copying django/conf/locale/eo/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/eo/LC_MESSAGES
copying django/conf/locale/eo/LC_MESSAGES/django.po -> build/lib/django/conf/locale/eo/LC_MESSAGES
creating build/lib/django/conf/locale/en_GB/LC_MESSAGES
copying django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
copying django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_GB/LC_MESSAGES
creating build/lib/django/conf/locale/en_AU/LC_MESSAGES
copying django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
copying django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en_AU/LC_MESSAGES
creating build/lib/django/conf/locale/en/LC_MESSAGES
copying django/conf/locale/en/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/en/LC_MESSAGES
copying django/conf/locale/en/LC_MESSAGES/django.po -> build/lib/django/conf/locale/en/LC_MESSAGES
creating build/lib/django/conf/locale/el/LC_MESSAGES
copying django/conf/locale/el/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/el/LC_MESSAGES
copying django/conf/locale/el/LC_MESSAGES/django.po -> build/lib/django/conf/locale/el/LC_MESSAGES
creating build/lib/django/conf/locale/de/LC_MESSAGES
copying django/conf/locale/de/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/de/LC_MESSAGES
copying django/conf/locale/de/LC_MESSAGES/django.po -> build/lib/django/conf/locale/de/LC_MESSAGES
creating build/lib/django/conf/locale/da/LC_MESSAGES
copying django/conf/locale/da/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/da/LC_MESSAGES
copying django/conf/locale/da/LC_MESSAGES/django.po -> build/lib/django/conf/locale/da/LC_MESSAGES
creating build/lib/django/conf/locale/cy/LC_MESSAGES
copying django/conf/locale/cy/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cy/LC_MESSAGES
copying django/conf/locale/cy/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cy/LC_MESSAGES
creating build/lib/django/conf/locale/cs/LC_MESSAGES
copying django/conf/locale/cs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/cs/LC_MESSAGES
copying django/conf/locale/cs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/cs/LC_MESSAGES
creating build/lib/django/conf/locale/ckb/LC_MESSAGES
copying django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ckb/LC_MESSAGES
copying django/conf/locale/ckb/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ckb/LC_MESSAGES
creating build/lib/django/conf/locale/ca/LC_MESSAGES
copying django/conf/locale/ca/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ca/LC_MESSAGES
copying django/conf/locale/ca/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ca/LC_MESSAGES
creating build/lib/django/conf/locale/bs/LC_MESSAGES
copying django/conf/locale/bs/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bs/LC_MESSAGES
copying django/conf/locale/bs/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bs/LC_MESSAGES
creating build/lib/django/conf/locale/bn/LC_MESSAGES
copying django/conf/locale/bn/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bn/LC_MESSAGES
copying django/conf/locale/bn/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bn/LC_MESSAGES
creating build/lib/django/conf/locale/bg/LC_MESSAGES
copying django/conf/locale/bg/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/bg/LC_MESSAGES
copying django/conf/locale/bg/LC_MESSAGES/django.po -> build/lib/django/conf/locale/bg/LC_MESSAGES
creating build/lib/django/conf/locale/az/LC_MESSAGES
copying django/conf/locale/az/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/az/LC_MESSAGES
copying django/conf/locale/az/LC_MESSAGES/django.po -> build/lib/django/conf/locale/az/LC_MESSAGES
creating build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
copying django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
copying django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar_DZ/LC_MESSAGES
creating build/lib/django/conf/locale/ar/LC_MESSAGES
copying django/conf/locale/ar/LC_MESSAGES/django.mo -> build/lib/django/conf/locale/ar/LC_MESSAGES
copying django/conf/locale/ar/LC_MESSAGES/django.po -> build/lib/django/conf/locale/ar/LC_MESSAGES
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
creating build/bdist.linux-x86_64/wheel/django
creating build/bdist.linux-x86_64/wheel/django/apps
copying build/lib/django/apps/__init__.py -> build/bdist.linux-x86_64/wheel/django/apps
copying build/lib/django/apps/config.py -> build/bdist.linux-x86_64/wheel/django/apps
copying build/lib/django/apps/registry.py -> build/bdist.linux-x86_64/wheel/django/apps
creating build/bdist.linux-x86_64/wheel/django/conf
creating build/bdist.linux-x86_64/wheel/django/conf/project_template
creating build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/wsgi.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/urls.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/settings.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/asgi.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name
copying build/lib/django/conf/project_template/project_name/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template/project_name
copying build/lib/django/conf/project_template/manage.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/project_template
creating build/bdist.linux-x86_64/wheel/django/conf/app_template
creating build/bdist.linux-x86_64/wheel/django/conf/app_template/migrations
copying build/lib/django/conf/app_template/migrations/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template/migrations
copying build/lib/django/conf/app_template/views.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template
copying build/lib/django/conf/app_template/tests.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template
copying build/lib/django/conf/app_template/models.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template
copying build/lib/django/conf/app_template/apps.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template
copying build/lib/django/conf/app_template/admin.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template
copying build/lib/django/conf/app_template/__init__.py-tpl -> build/bdist.linux-x86_64/wheel/django/conf/app_template
creating build/bdist.linux-x86_64/wheel/django/conf/locale
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ur
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ur/LC_MESSAGES
copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ur/LC_MESSAGES
copying build/lib/django/conf/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/udm
creating build/bdist.linux-x86_64/wheel/django/conf/locale/udm/LC_MESSAGES
copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/udm/LC_MESSAGES
copying build/lib/django/conf/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tt
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tt/LC_MESSAGES
copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tt/LC_MESSAGES
copying build/lib/django/conf/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sw
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sw/LC_MESSAGES
copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sw/LC_MESSAGES
copying build/lib/django/conf/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pa
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pa/LC_MESSAGES
copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pa/LC_MESSAGES
copying build/lib/django/conf/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/os
creating build/bdist.linux-x86_64/wheel/django/conf/locale/os/LC_MESSAGES
copying build/lib/django/conf/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/os/LC_MESSAGES
copying build/lib/django/conf/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ne
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ne/LC_MESSAGES
copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ne/LC_MESSAGES
copying build/lib/django/conf/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/my
creating build/bdist.linux-x86_64/wheel/django/conf/locale/my/LC_MESSAGES
copying build/lib/django/conf/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/my/LC_MESSAGES
copying build/lib/django/conf/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/mr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/mr/LC_MESSAGES
copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/mr/LC_MESSAGES
copying build/lib/django/conf/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/lb
creating build/bdist.linux-x86_64/wheel/django/conf/locale/lb/LC_MESSAGES
copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/lb/LC_MESSAGES
copying build/lib/django/conf/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/kk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/kk/LC_MESSAGES
copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/kk/LC_MESSAGES
copying build/lib/django/conf/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/kab
creating build/bdist.linux-x86_64/wheel/django/conf/locale/kab/LC_MESSAGES
copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/kab/LC_MESSAGES
copying build/lib/django/conf/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/kab/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/io
creating build/bdist.linux-x86_64/wheel/django/conf/locale/io/LC_MESSAGES
copying build/lib/django/conf/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/io/LC_MESSAGES
copying build/lib/django/conf/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ia
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ia/LC_MESSAGES
copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ia/LC_MESSAGES
copying build/lib/django/conf/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hy
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hy/LC_MESSAGES
copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hy/LC_MESSAGES
copying build/lib/django/conf/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hsb/LC_MESSAGES
copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hsb/LC_MESSAGES
copying build/lib/django/conf/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE/LC_MESSAGES
copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE/LC_MESSAGES
copying build/lib/django/conf/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/conf/locale/dsb/LC_MESSAGES
copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/dsb/LC_MESSAGES
copying build/lib/django/conf/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/br
creating build/bdist.linux-x86_64/wheel/django/conf/locale/br/LC_MESSAGES
copying build/lib/django/conf/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/br/LC_MESSAGES
copying build/lib/django/conf/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/be
creating build/bdist.linux-x86_64/wheel/django/conf/locale/be/LC_MESSAGES
copying build/lib/django/conf/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/be/LC_MESSAGES
copying build/lib/django/conf/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ast
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ast/LC_MESSAGES
copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ast/LC_MESSAGES
copying build/lib/django/conf/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/af
creating build/bdist.linux-x86_64/wheel/django/conf/locale/af/LC_MESSAGES
copying build/lib/django/conf/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/af/LC_MESSAGES
copying build/lib/django/conf/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar/LC_MESSAGES
copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar/LC_MESSAGES
copying build/lib/django/conf/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar/LC_MESSAGES
copying build/lib/django/conf/locale/ar/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar
copying build/lib/django/conf/locale/ar/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/conf/locale/ar_DZ/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ
copying build/lib/django/conf/locale/ar_DZ/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/conf/locale/az
creating build/bdist.linux-x86_64/wheel/django/conf/locale/az/LC_MESSAGES
copying build/lib/django/conf/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/az/LC_MESSAGES
copying build/lib/django/conf/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/az/LC_MESSAGES
copying build/lib/django/conf/locale/az/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/az
copying build/lib/django/conf/locale/az/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/az
creating build/bdist.linux-x86_64/wheel/django/conf/locale/bg
creating build/bdist.linux-x86_64/wheel/django/conf/locale/bg/LC_MESSAGES
copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg/LC_MESSAGES
copying build/lib/django/conf/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg/LC_MESSAGES
copying build/lib/django/conf/locale/bg/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg
copying build/lib/django/conf/locale/bg/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bg
creating build/bdist.linux-x86_64/wheel/django/conf/locale/bn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/bn/LC_MESSAGES
copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn/LC_MESSAGES
copying build/lib/django/conf/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn/LC_MESSAGES
copying build/lib/django/conf/locale/bn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn
copying build/lib/django/conf/locale/bn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/bs
creating build/bdist.linux-x86_64/wheel/django/conf/locale/bs/LC_MESSAGES
copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs/LC_MESSAGES
copying build/lib/django/conf/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs/LC_MESSAGES
copying build/lib/django/conf/locale/bs/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs
copying build/lib/django/conf/locale/bs/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/bs
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ca
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ca/LC_MESSAGES
copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca/LC_MESSAGES
copying build/lib/django/conf/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca/LC_MESSAGES
copying build/lib/django/conf/locale/ca/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca
copying build/lib/django/conf/locale/ca/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ca
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ckb/LC_MESSAGES
copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb/LC_MESSAGES
copying build/lib/django/conf/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb/LC_MESSAGES
copying build/lib/django/conf/locale/ckb/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb
copying build/lib/django/conf/locale/ckb/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/conf/locale/cs
creating build/bdist.linux-x86_64/wheel/django/conf/locale/cs/LC_MESSAGES
copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs/LC_MESSAGES
copying build/lib/django/conf/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs/LC_MESSAGES
copying build/lib/django/conf/locale/cs/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs
copying build/lib/django/conf/locale/cs/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cs
creating build/bdist.linux-x86_64/wheel/django/conf/locale/cy
creating build/bdist.linux-x86_64/wheel/django/conf/locale/cy/LC_MESSAGES
copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy/LC_MESSAGES
copying build/lib/django/conf/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy/LC_MESSAGES
copying build/lib/django/conf/locale/cy/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy
copying build/lib/django/conf/locale/cy/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/cy
creating build/bdist.linux-x86_64/wheel/django/conf/locale/da
creating build/bdist.linux-x86_64/wheel/django/conf/locale/da/LC_MESSAGES
copying build/lib/django/conf/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/da/LC_MESSAGES
copying build/lib/django/conf/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/da/LC_MESSAGES
copying build/lib/django/conf/locale/da/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/da
copying build/lib/django/conf/locale/da/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/da
creating build/bdist.linux-x86_64/wheel/django/conf/locale/de
creating build/bdist.linux-x86_64/wheel/django/conf/locale/de/LC_MESSAGES
copying build/lib/django/conf/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/de/LC_MESSAGES
copying build/lib/django/conf/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/de/LC_MESSAGES
copying build/lib/django/conf/locale/de/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de
copying build/lib/django/conf/locale/de/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de
creating build/bdist.linux-x86_64/wheel/django/conf/locale/de_CH
copying build/lib/django/conf/locale/de_CH/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de_CH
copying build/lib/django/conf/locale/de_CH/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/de_CH
creating build/bdist.linux-x86_64/wheel/django/conf/locale/el
creating build/bdist.linux-x86_64/wheel/django/conf/locale/el/LC_MESSAGES
copying build/lib/django/conf/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/el/LC_MESSAGES
copying build/lib/django/conf/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/el/LC_MESSAGES
copying build/lib/django/conf/locale/el/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/el
copying build/lib/django/conf/locale/el/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/el
creating build/bdist.linux-x86_64/wheel/django/conf/locale/en
creating build/bdist.linux-x86_64/wheel/django/conf/locale/en/LC_MESSAGES
copying build/lib/django/conf/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/en/LC_MESSAGES
copying build/lib/django/conf/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/en/LC_MESSAGES
copying build/lib/django/conf/locale/en/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en
copying build/lib/django/conf/locale/en/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en
creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU/LC_MESSAGES
copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU/LC_MESSAGES
copying build/lib/django/conf/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU/LC_MESSAGES
copying build/lib/django/conf/locale/en_AU/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU
copying build/lib/django/conf/locale/en_AU/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB/LC_MESSAGES
copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB/LC_MESSAGES
copying build/lib/django/conf/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB/LC_MESSAGES
copying build/lib/django/conf/locale/en_GB/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB
copying build/lib/django/conf/locale/en_GB/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/conf/locale/eo
creating build/bdist.linux-x86_64/wheel/django/conf/locale/eo/LC_MESSAGES
copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo/LC_MESSAGES
copying build/lib/django/conf/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo/LC_MESSAGES
copying build/lib/django/conf/locale/eo/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo
copying build/lib/django/conf/locale/eo/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eo
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es/LC_MESSAGES
copying build/lib/django/conf/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es/LC_MESSAGES
copying build/lib/django/conf/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es/LC_MESSAGES
copying build/lib/django/conf/locale/es/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es
copying build/lib/django/conf/locale/es/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR/LC_MESSAGES
copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR/LC_MESSAGES
copying build/lib/django/conf/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR/LC_MESSAGES
copying build/lib/django/conf/locale/es_AR/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR
copying build/lib/django/conf/locale/es_AR/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO/LC_MESSAGES
copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO/LC_MESSAGES
copying build/lib/django/conf/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO/LC_MESSAGES
copying build/lib/django/conf/locale/es_CO/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO
copying build/lib/django/conf/locale/es_CO/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX/LC_MESSAGES
copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX/LC_MESSAGES
copying build/lib/django/conf/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX/LC_MESSAGES
copying build/lib/django/conf/locale/es_MX/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX
copying build/lib/django/conf/locale/es_MX/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_NI
copying build/lib/django/conf/locale/es_NI/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_NI
copying build/lib/django/conf/locale/es_NI/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_NI
creating build/bdist.linux-x86_64/wheel/django/conf/locale/es_PR
copying build/lib/django/conf/locale/es_PR/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_PR
copying build/lib/django/conf/locale/es_PR/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/es_PR
creating build/bdist.linux-x86_64/wheel/django/conf/locale/et
creating build/bdist.linux-x86_64/wheel/django/conf/locale/et/LC_MESSAGES
copying build/lib/django/conf/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/et/LC_MESSAGES
copying build/lib/django/conf/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/et/LC_MESSAGES
copying build/lib/django/conf/locale/et/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/et
copying build/lib/django/conf/locale/et/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/et
creating build/bdist.linux-x86_64/wheel/django/conf/locale/eu
creating build/bdist.linux-x86_64/wheel/django/conf/locale/eu/LC_MESSAGES
copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu/LC_MESSAGES
copying build/lib/django/conf/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu/LC_MESSAGES
copying build/lib/django/conf/locale/eu/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu
copying build/lib/django/conf/locale/eu/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/eu
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fa
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fa/LC_MESSAGES
copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa/LC_MESSAGES
copying build/lib/django/conf/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa/LC_MESSAGES
copying build/lib/django/conf/locale/fa/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa
copying build/lib/django/conf/locale/fa/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fa
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fi
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fi/LC_MESSAGES
copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi/LC_MESSAGES
copying build/lib/django/conf/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi/LC_MESSAGES
copying build/lib/django/conf/locale/fi/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi
copying build/lib/django/conf/locale/fi/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fi
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fr/LC_MESSAGES
copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr/LC_MESSAGES
copying build/lib/django/conf/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr/LC_MESSAGES
copying build/lib/django/conf/locale/fr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr
copying build/lib/django/conf/locale/fr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fy
creating build/bdist.linux-x86_64/wheel/django/conf/locale/fy/LC_MESSAGES
copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy/LC_MESSAGES
copying build/lib/django/conf/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy/LC_MESSAGES
copying build/lib/django/conf/locale/fy/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy
copying build/lib/django/conf/locale/fy/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/fy
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ga
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ga/LC_MESSAGES
copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga/LC_MESSAGES
copying build/lib/django/conf/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga/LC_MESSAGES
copying build/lib/django/conf/locale/ga/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga
copying build/lib/django/conf/locale/ga/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ga
creating build/bdist.linux-x86_64/wheel/django/conf/locale/gd
creating build/bdist.linux-x86_64/wheel/django/conf/locale/gd/LC_MESSAGES
copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd/LC_MESSAGES
copying build/lib/django/conf/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd/LC_MESSAGES
copying build/lib/django/conf/locale/gd/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd
copying build/lib/django/conf/locale/gd/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gd
creating build/bdist.linux-x86_64/wheel/django/conf/locale/gl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/gl/LC_MESSAGES
copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl/LC_MESSAGES
copying build/lib/django/conf/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl/LC_MESSAGES
copying build/lib/django/conf/locale/gl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl
copying build/lib/django/conf/locale/gl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/gl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/he
creating build/bdist.linux-x86_64/wheel/django/conf/locale/he/LC_MESSAGES
copying build/lib/django/conf/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/he/LC_MESSAGES
copying build/lib/django/conf/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/he/LC_MESSAGES
copying build/lib/django/conf/locale/he/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/he
copying build/lib/django/conf/locale/he/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/he
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hi
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hi/LC_MESSAGES
copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi/LC_MESSAGES
copying build/lib/django/conf/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi/LC_MESSAGES
copying build/lib/django/conf/locale/hi/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi
copying build/lib/django/conf/locale/hi/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hi
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hr/LC_MESSAGES
copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr/LC_MESSAGES
copying build/lib/django/conf/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr/LC_MESSAGES
copying build/lib/django/conf/locale/hr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr
copying build/lib/django/conf/locale/hr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hu
creating build/bdist.linux-x86_64/wheel/django/conf/locale/hu/LC_MESSAGES
copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu/LC_MESSAGES
copying build/lib/django/conf/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu/LC_MESSAGES
copying build/lib/django/conf/locale/hu/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu
copying build/lib/django/conf/locale/hu/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/hu
creating build/bdist.linux-x86_64/wheel/django/conf/locale/id
creating build/bdist.linux-x86_64/wheel/django/conf/locale/id/LC_MESSAGES
copying build/lib/django/conf/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/id/LC_MESSAGES
copying build/lib/django/conf/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/id/LC_MESSAGES
copying build/lib/django/conf/locale/id/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/id
copying build/lib/django/conf/locale/id/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/id
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ig
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ig/LC_MESSAGES
copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig/LC_MESSAGES
copying build/lib/django/conf/locale/ig/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig/LC_MESSAGES
copying build/lib/django/conf/locale/ig/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig
copying build/lib/django/conf/locale/ig/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ig
creating build/bdist.linux-x86_64/wheel/django/conf/locale/is
creating build/bdist.linux-x86_64/wheel/django/conf/locale/is/LC_MESSAGES
copying build/lib/django/conf/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/is/LC_MESSAGES
copying build/lib/django/conf/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/is/LC_MESSAGES
copying build/lib/django/conf/locale/is/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/is
copying build/lib/django/conf/locale/is/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/is
creating build/bdist.linux-x86_64/wheel/django/conf/locale/it
creating build/bdist.linux-x86_64/wheel/django/conf/locale/it/LC_MESSAGES
copying build/lib/django/conf/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/it/LC_MESSAGES
copying build/lib/django/conf/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/it/LC_MESSAGES
copying build/lib/django/conf/locale/it/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/it
copying build/lib/django/conf/locale/it/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/it
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ja
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ja/LC_MESSAGES
copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja/LC_MESSAGES
copying build/lib/django/conf/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja/LC_MESSAGES
copying build/lib/django/conf/locale/ja/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja
copying build/lib/django/conf/locale/ja/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ja
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ka
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ka/LC_MESSAGES
copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka/LC_MESSAGES
copying build/lib/django/conf/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka/LC_MESSAGES
copying build/lib/django/conf/locale/ka/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka
copying build/lib/django/conf/locale/ka/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ka
creating build/bdist.linux-x86_64/wheel/django/conf/locale/km
creating build/bdist.linux-x86_64/wheel/django/conf/locale/km/LC_MESSAGES
copying build/lib/django/conf/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/km/LC_MESSAGES
copying build/lib/django/conf/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/km/LC_MESSAGES
copying build/lib/django/conf/locale/km/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/km
copying build/lib/django/conf/locale/km/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/km
creating build/bdist.linux-x86_64/wheel/django/conf/locale/kn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/kn/LC_MESSAGES
copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn/LC_MESSAGES
copying build/lib/django/conf/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn/LC_MESSAGES
copying build/lib/django/conf/locale/kn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn
copying build/lib/django/conf/locale/kn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/kn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ko
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ko/LC_MESSAGES
copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko/LC_MESSAGES
copying build/lib/django/conf/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko/LC_MESSAGES
copying build/lib/django/conf/locale/ko/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko
copying build/lib/django/conf/locale/ko/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ko
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ky
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ky/LC_MESSAGES
copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky/LC_MESSAGES
copying build/lib/django/conf/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky/LC_MESSAGES
copying build/lib/django/conf/locale/ky/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky
copying build/lib/django/conf/locale/ky/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ky
creating build/bdist.linux-x86_64/wheel/django/conf/locale/lt
creating build/bdist.linux-x86_64/wheel/django/conf/locale/lt/LC_MESSAGES
copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt/LC_MESSAGES
copying build/lib/django/conf/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt/LC_MESSAGES
copying build/lib/django/conf/locale/lt/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt
copying build/lib/django/conf/locale/lt/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lt
creating build/bdist.linux-x86_64/wheel/django/conf/locale/lv
creating build/bdist.linux-x86_64/wheel/django/conf/locale/lv/LC_MESSAGES
copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv/LC_MESSAGES
copying build/lib/django/conf/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv/LC_MESSAGES
copying build/lib/django/conf/locale/lv/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv
copying build/lib/django/conf/locale/lv/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/lv
creating build/bdist.linux-x86_64/wheel/django/conf/locale/mk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/mk/LC_MESSAGES
copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk/LC_MESSAGES
copying build/lib/django/conf/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk/LC_MESSAGES
copying build/lib/django/conf/locale/mk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk
copying build/lib/django/conf/locale/mk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ml
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ml/LC_MESSAGES
copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml/LC_MESSAGES
copying build/lib/django/conf/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml/LC_MESSAGES
copying build/lib/django/conf/locale/ml/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml
copying build/lib/django/conf/locale/ml/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ml
creating build/bdist.linux-x86_64/wheel/django/conf/locale/mn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/mn/LC_MESSAGES
copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn/LC_MESSAGES
copying build/lib/django/conf/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn/LC_MESSAGES
copying build/lib/django/conf/locale/mn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn
copying build/lib/django/conf/locale/mn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/mn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ms
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ms/LC_MESSAGES
copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms/LC_MESSAGES
copying build/lib/django/conf/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms/LC_MESSAGES
copying build/lib/django/conf/locale/ms/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms
copying build/lib/django/conf/locale/ms/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ms
creating build/bdist.linux-x86_64/wheel/django/conf/locale/nb
creating build/bdist.linux-x86_64/wheel/django/conf/locale/nb/LC_MESSAGES
copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb/LC_MESSAGES
copying build/lib/django/conf/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb/LC_MESSAGES
copying build/lib/django/conf/locale/nb/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb
copying build/lib/django/conf/locale/nb/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nb
creating build/bdist.linux-x86_64/wheel/django/conf/locale/nl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/nl/LC_MESSAGES
copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl/LC_MESSAGES
copying build/lib/django/conf/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl/LC_MESSAGES
copying build/lib/django/conf/locale/nl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl
copying build/lib/django/conf/locale/nl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/nn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/nn/LC_MESSAGES
copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn/LC_MESSAGES
copying build/lib/django/conf/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn/LC_MESSAGES
copying build/lib/django/conf/locale/nn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn
copying build/lib/django/conf/locale/nn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/nn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pl/LC_MESSAGES
copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl/LC_MESSAGES
copying build/lib/django/conf/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl/LC_MESSAGES
copying build/lib/django/conf/locale/pl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl
copying build/lib/django/conf/locale/pl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt/LC_MESSAGES
copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt/LC_MESSAGES
copying build/lib/django/conf/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt/LC_MESSAGES
copying build/lib/django/conf/locale/pt/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt
copying build/lib/django/conf/locale/pt/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR/LC_MESSAGES
copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR/LC_MESSAGES
copying build/lib/django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR/LC_MESSAGES
copying build/lib/django/conf/locale/pt_BR/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR
copying build/lib/django/conf/locale/pt_BR/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ro
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ro/LC_MESSAGES
copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro/LC_MESSAGES
copying build/lib/django/conf/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro/LC_MESSAGES
copying build/lib/django/conf/locale/ro/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro
copying build/lib/django/conf/locale/ro/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ro
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ru
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ru/LC_MESSAGES
copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru/LC_MESSAGES
copying build/lib/django/conf/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru/LC_MESSAGES
copying build/lib/django/conf/locale/ru/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru
copying build/lib/django/conf/locale/ru/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ru
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sk/LC_MESSAGES
copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk/LC_MESSAGES
copying build/lib/django/conf/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk/LC_MESSAGES
copying build/lib/django/conf/locale/sk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk
copying build/lib/django/conf/locale/sk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sl/LC_MESSAGES
copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl/LC_MESSAGES
copying build/lib/django/conf/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl/LC_MESSAGES
copying build/lib/django/conf/locale/sl/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl
copying build/lib/django/conf/locale/sl/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sl
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sq
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sq/LC_MESSAGES
copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq/LC_MESSAGES
copying build/lib/django/conf/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq/LC_MESSAGES
copying build/lib/django/conf/locale/sq/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq
copying build/lib/django/conf/locale/sq/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sq
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr/LC_MESSAGES
copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr/LC_MESSAGES
copying build/lib/django/conf/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr/LC_MESSAGES
copying build/lib/django/conf/locale/sr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr
copying build/lib/django/conf/locale/sr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/conf/locale/sr_Latn/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn
copying build/lib/django/conf/locale/sr_Latn/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sv
creating build/bdist.linux-x86_64/wheel/django/conf/locale/sv/LC_MESSAGES
copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv/LC_MESSAGES
copying build/lib/django/conf/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv/LC_MESSAGES
copying build/lib/django/conf/locale/sv/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv
copying build/lib/django/conf/locale/sv/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/sv
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ta
creating build/bdist.linux-x86_64/wheel/django/conf/locale/ta/LC_MESSAGES
copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta/LC_MESSAGES
copying build/lib/django/conf/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta/LC_MESSAGES
copying build/lib/django/conf/locale/ta/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta
copying build/lib/django/conf/locale/ta/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/ta
creating build/bdist.linux-x86_64/wheel/django/conf/locale/te
creating build/bdist.linux-x86_64/wheel/django/conf/locale/te/LC_MESSAGES
copying build/lib/django/conf/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/te/LC_MESSAGES
copying build/lib/django/conf/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/te/LC_MESSAGES
copying build/lib/django/conf/locale/te/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/te
copying build/lib/django/conf/locale/te/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/te
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tg
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tg/LC_MESSAGES
copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg/LC_MESSAGES
copying build/lib/django/conf/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg/LC_MESSAGES
copying build/lib/django/conf/locale/tg/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg
copying build/lib/django/conf/locale/tg/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tg
creating build/bdist.linux-x86_64/wheel/django/conf/locale/th
creating build/bdist.linux-x86_64/wheel/django/conf/locale/th/LC_MESSAGES
copying build/lib/django/conf/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/th/LC_MESSAGES
copying build/lib/django/conf/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/th/LC_MESSAGES
copying build/lib/django/conf/locale/th/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/th
copying build/lib/django/conf/locale/th/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/th
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tk/LC_MESSAGES
copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk/LC_MESSAGES
copying build/lib/django/conf/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk/LC_MESSAGES
copying build/lib/django/conf/locale/tk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk
copying build/lib/django/conf/locale/tk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/tr/LC_MESSAGES
copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr/LC_MESSAGES
copying build/lib/django/conf/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr/LC_MESSAGES
copying build/lib/django/conf/locale/tr/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr
copying build/lib/django/conf/locale/tr/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/tr
creating build/bdist.linux-x86_64/wheel/django/conf/locale/uk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/uk/LC_MESSAGES
copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk/LC_MESSAGES
copying build/lib/django/conf/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk/LC_MESSAGES
copying build/lib/django/conf/locale/uk/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk
copying build/lib/django/conf/locale/uk/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uk
creating build/bdist.linux-x86_64/wheel/django/conf/locale/uz
creating build/bdist.linux-x86_64/wheel/django/conf/locale/uz/LC_MESSAGES
copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz/LC_MESSAGES
copying build/lib/django/conf/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz/LC_MESSAGES
copying build/lib/django/conf/locale/uz/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz
copying build/lib/django/conf/locale/uz/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/uz
creating build/bdist.linux-x86_64/wheel/django/conf/locale/vi
creating build/bdist.linux-x86_64/wheel/django/conf/locale/vi/LC_MESSAGES
copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi/LC_MESSAGES
copying build/lib/django/conf/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi/LC_MESSAGES
copying build/lib/django/conf/locale/vi/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi
copying build/lib/django/conf/locale/vi/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/vi
creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hans/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans
copying build/lib/django/conf/locale/zh_Hans/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/conf/locale/zh_Hant/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant
copying build/lib/django/conf/locale/zh_Hant/formats.py -> build/bdist.linux-x86_64/wheel/django/conf/locale/zh_Hant
copying build/lib/django/conf/locale/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/locale
creating build/bdist.linux-x86_64/wheel/django/conf/urls
copying build/lib/django/conf/urls/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf/urls
copying build/lib/django/conf/urls/i18n.py -> build/bdist.linux-x86_64/wheel/django/conf/urls
copying build/lib/django/conf/urls/static.py -> build/bdist.linux-x86_64/wheel/django/conf/urls
copying build/lib/django/conf/__init__.py -> build/bdist.linux-x86_64/wheel/django/conf
copying build/lib/django/conf/global_settings.py -> build/bdist.linux-x86_64/wheel/django/conf
creating build/bdist.linux-x86_64/wheel/django/contrib
creating build/bdist.linux-x86_64/wheel/django/contrib/admin
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_email.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_done.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_confirm.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_reset_complete.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_change_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/password_change_done.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
copying build/lib/django/contrib/admin/templates/registration/logged_out.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/registration
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/url.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/time.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/split_datetime.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/radio.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/date.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
copying build/lib/django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/widgets
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/includes
copying build/lib/django/contrib/admin/templates/admin/includes/object_delete_summary.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/includes
copying build/lib/django/contrib/admin/templates/admin/includes/fieldset.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/includes
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/edit_inline
copying build/lib/django/contrib/admin/templates/admin/edit_inline/tabular.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/edit_inline
copying build/lib/django/contrib/admin/templates/admin/edit_inline/stacked.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/edit_inline
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth/user
copying build/lib/django/contrib/admin/templates/admin/auth/user/change_password.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth/user
copying build/lib/django/contrib/admin/templates/admin/auth/user/add_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin/auth/user
copying build/lib/django/contrib/admin/templates/admin/submit_line.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/search_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/prepopulated_fields_js.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/popup_response.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/pagination.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/object_history.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/nav_sidebar.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/login.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/invalid_setup.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/filter.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/delete_selected_confirmation.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/delete_confirmation.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/date_hierarchy.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/color_theme_toggle.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_list_results.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_list_object_tools.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_list.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_form_object_tools.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/change_form.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/base_site.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/base.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/app_list.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/app_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/actions.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/500.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
copying build/lib/django/contrib/admin/templates/admin/404.html -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templates/admin
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
copying build/lib/django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/xregexp
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2/i18n
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2
copying build/lib/django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/select2
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
copying build/lib/django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/vendor/jquery
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/admin
copying build/lib/django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/admin
copying build/lib/django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js/admin
copying build/lib/django/contrib/admin/static/admin/js/urlify.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/theme.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/prepopulate_init.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/prepopulate.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/popup_response.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/nav_sidebar.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/jquery.init.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/inlines.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/filters.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/core.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/collapse.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/change_form.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/cancel.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/calendar.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/autocomplete.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/actions.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/SelectFilter2.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
copying build/lib/django/contrib/admin/static/admin/js/SelectBox.js -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/js
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img/gis
copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img/gis
copying build/lib/django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img/gis
copying build/lib/django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/tooltag-add.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/sorting-icons.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/selector-icons.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/search.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/inline-delete.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-yes.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-viewlink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-unknown.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-no.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-deletelink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-clock.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-changelink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-calendar.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-alert.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/icon-addlink.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/calendar-icons.svg -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/README.txt -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
copying build/lib/django/contrib/admin/static/admin/img/LICENSE -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/img
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2
copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2
copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/select2.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2
copying build/lib/django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css/vendor/select2
copying build/lib/django/contrib/admin/static/admin/css/widgets.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/rtl.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/responsive_rtl.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/responsive.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/nav_sidebar.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/login.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/forms.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/dashboard.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/dark_mode.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/changelists.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/base.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
copying build/lib/django/contrib/admin/static/admin/css/autocomplete.css -> build/bdist.linux-x86_64/wheel/django/contrib/admin/static/admin/css
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uz/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/kab/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/am/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admin/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations
copying build/lib/django/contrib/admin/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/migrations
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/admin_list.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/admin_modify.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/admin_urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
copying build/lib/django/contrib/admin/templatetags/log.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/templatetags
creating build/bdist.linux-x86_64/wheel/django/contrib/admin/views
copying build/lib/django/contrib/admin/views/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views
copying build/lib/django/contrib/admin/views/autocomplete.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views
copying build/lib/django/contrib/admin/views/decorators.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views
copying build/lib/django/contrib/admin/views/main.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin/views
copying build/lib/django/contrib/admin/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/actions.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/decorators.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/exceptions.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/filters.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/helpers.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/options.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/sites.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/tests.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
copying build/lib/django/contrib/admin/widgets.py -> build/bdist.linux-x86_64/wheel/django/contrib/admin
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/view_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/view_detail.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/template_detail.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/model_index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/model_detail.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/index.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
copying build/lib/django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/templates/admin_doc
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/kab/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs/locale/af/LC_MESSAGES
copying build/lib/django/contrib/admindocs/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs
copying build/lib/django/contrib/admindocs/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs
copying build/lib/django/contrib/admindocs/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs
copying build/lib/django/contrib/admindocs/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs
copying build/lib/django/contrib/admindocs/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs
copying build/lib/django/contrib/admindocs/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/admindocs
creating build/bdist.linux-x86_64/wheel/django/contrib/auth
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/registration
copying build/lib/django/contrib/auth/templates/registration/password_reset_subject.txt -> build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/registration
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth/widgets
copying build/lib/django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> build/bdist.linux-x86_64/wheel/django/contrib/auth/templates/auth/widgets
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uz/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/kab/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af/LC_MESSAGES
copying build/lib/django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/auth/locale/af/LC_MESSAGES
copying build/lib/django/contrib/auth/common-passwords.txt.gz -> build/bdist.linux-x86_64/wheel/django/contrib/auth
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/handlers
copying build/lib/django/contrib/auth/handlers/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/handlers
copying build/lib/django/contrib/auth/handlers/modwsgi.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/handlers
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/management
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands
copying build/lib/django/contrib/auth/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands
copying build/lib/django/contrib/auth/management/commands/changepassword.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands
copying build/lib/django/contrib/auth/management/commands/createsuperuser.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management/commands
copying build/lib/django/contrib/auth/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/management
creating build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0004_alter_user_username_opts.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0011_update_proxy_permissions.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth/migrations
copying build/lib/django/contrib/auth/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/backends.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/base_user.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/context_processors.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/decorators.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/hashers.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/mixins.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/password_validation.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/signals.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/tokens.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/validators.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
copying build/lib/django/contrib/auth/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/auth
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
copying build/lib/django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management/commands
copying build/lib/django/contrib/contenttypes/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management/commands
copying build/lib/django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management/commands
copying build/lib/django/contrib/contenttypes/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/management
creating build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations
copying build/lib/django/contrib/contenttypes/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations
copying build/lib/django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations
copying build/lib/django/contrib/contenttypes/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes/migrations
copying build/lib/django/contrib/contenttypes/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/fields.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
copying build/lib/django/contrib/contenttypes/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/contenttypes
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
copying build/lib/django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/migrations
copying build/lib/django/contrib/flatpages/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/migrations
copying build/lib/django/contrib/flatpages/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/migrations
creating build/bdist.linux-x86_64/wheel/django/contrib/flatpages/templatetags
copying build/lib/django/contrib/flatpages/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/templatetags
copying build/lib/django/contrib/flatpages/templatetags/flatpages.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages/templatetags
copying build/lib/django/contrib/flatpages/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/forms.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/sitemaps.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
copying build/lib/django/contrib/flatpages/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/flatpages
creating build/bdist.linux-x86_64/wheel/django/contrib/gis
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/kml
copying build/lib/django/contrib/gis/templates/gis/kml/placemarks.kml -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/kml
copying build/lib/django/contrib/gis/templates/gis/kml/base.kml -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/kml
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/osm.js -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/osm.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.js -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/admin/openlayers.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis/admin
copying build/lib/django/contrib/gis/templates/gis/openlayers.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis
copying build/lib/django/contrib/gis/templates/gis/openlayers-osm.html -> build/bdist.linux-x86_64/wheel/django/contrib/gis/templates/gis
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/js
copying build/lib/django/contrib/gis/static/gis/js/OLMapWidget.js -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/js
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_polygon_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_point_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_point_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_line_on.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
copying build/lib/django/contrib/gis/static/gis/img/draw_line_off.svg -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/img
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/css
copying build/lib/django/contrib/gis/static/gis/css/ol3.css -> build/bdist.linux-x86_64/wheel/django/contrib/gis/static/gis/css
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af/LC_MESSAGES
copying build/lib/django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/gis/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/admin
copying build/lib/django/contrib/gis/admin/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/admin
copying build/lib/django/contrib/gis/admin/options.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/admin
copying build/lib/django/contrib/gis/admin/widgets.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/admin
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base
copying build/lib/django/contrib/gis/db/backends/base/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/base
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
copying build/lib/django/contrib/gis/db/backends/mysql/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/mysql
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
copying build/lib/django/contrib/gis/db/backends/oracle/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/oracle
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/const.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/pgraster.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
copying build/lib/django/contrib/gis/db/backends/postgis/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/postgis
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/adapter.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/client.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/features.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/introspection.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/spatialite/schema.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends/spatialite
copying build/lib/django/contrib/gis/db/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends
copying build/lib/django/contrib/gis/db/backends/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/backends
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models/sql
copying build/lib/django/contrib/gis/db/models/sql/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models/sql
copying build/lib/django/contrib/gis/db/models/sql/conversion.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models/sql
copying build/lib/django/contrib/gis/db/models/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/aggregates.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/fields.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/functions.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/lookups.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/models/proxy.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db/models
copying build/lib/django/contrib/gis/db/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/db
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/forms
copying build/lib/django/contrib/gis/forms/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/forms
copying build/lib/django/contrib/gis/forms/fields.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/forms
copying build/lib/django/contrib/gis/forms/widgets.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/forms
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/LICENSE -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/ds.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/errcheck.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/generation.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/geom.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/raster.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
copying build/lib/django/contrib/gis/gdal/prototypes/srs.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/prototypes
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/band.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/const.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/raster/source.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal/raster
copying build/lib/django/contrib/gis/gdal/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/datasource.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/driver.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/envelope.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/error.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/feature.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/field.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/geometries.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/geomtype.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/layer.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/libgdal.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
copying build/lib/django/contrib/gis/gdal/srs.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/gdal
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2
copying build/lib/django/contrib/gis/geoip2/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2
copying build/lib/django/contrib/gis/geoip2/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2
copying build/lib/django/contrib/gis/geoip2/resources.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geoip2
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/LICENSE -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/coordseq.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/errcheck.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/geom.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/io.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/misc.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/predicates.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/prepared.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/threadsafe.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/prototypes/topology.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos/prototypes
copying build/lib/django/contrib/gis/geos/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/collections.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/coordseq.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/error.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/factory.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/geometry.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/io.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/libgeos.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/linestring.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/mutable_list.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/point.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/polygon.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
copying build/lib/django/contrib/gis/geos/prepared.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/geos
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/management
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands
copying build/lib/django/contrib/gis/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands
copying build/lib/django/contrib/gis/management/commands/inspectdb.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands
copying build/lib/django/contrib/gis/management/commands/ogrinspect.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management/commands
copying build/lib/django/contrib/gis/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/management
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/serializers
copying build/lib/django/contrib/gis/serializers/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/serializers
copying build/lib/django/contrib/gis/serializers/geojson.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/serializers
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps
copying build/lib/django/contrib/gis/sitemaps/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps
copying build/lib/django/contrib/gis/sitemaps/kml.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps
copying build/lib/django/contrib/gis/sitemaps/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/sitemaps
creating build/bdist.linux-x86_64/wheel/django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/layermapping.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/ogrinfo.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/ogrinspect.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils
copying build/lib/django/contrib/gis/utils/srs.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis/utils
copying build/lib/django/contrib/gis/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/feeds.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/geometry.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/measure.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/ptr.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/shortcuts.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
copying build/lib/django/contrib/gis/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/gis
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uz/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
copying build/lib/django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/humanize/templatetags
copying build/lib/django/contrib/humanize/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/templatetags
copying build/lib/django/contrib/humanize/templatetags/humanize.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize/templatetags
copying build/lib/django/contrib/humanize/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize
copying build/lib/django/contrib/humanize/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/humanize
creating build/bdist.linux-x86_64/wheel/django/contrib/messages
creating build/bdist.linux-x86_64/wheel/django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/cookie.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/fallback.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage
copying build/lib/django/contrib/messages/storage/session.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages/storage
copying build/lib/django/contrib/messages/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/api.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/constants.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/context_processors.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
copying build/lib/django/contrib/messages/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/messages
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres/widgets
copying build/lib/django/contrib/postgres/templates/postgres/widgets/split_array.html -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/templates/postgres/widgets
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uz/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
copying build/lib/django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres/widgets
copying build/lib/django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/jinja2/postgres/widgets
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/general.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/mixins.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates
copying build/lib/django/contrib/postgres/aggregates/statistics.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/aggregates
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/array.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/citext.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/hstore.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/jsonb.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/ranges.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
copying build/lib/django/contrib/postgres/fields/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/fields
creating build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/array.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/hstore.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/forms/ranges.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres/forms
copying build/lib/django/contrib/postgres/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/constraints.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/expressions.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/functions.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/indexes.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/lookups.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/operations.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/search.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/serializers.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/signals.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
copying build/lib/django/contrib/postgres/validators.py -> build/bdist.linux-x86_64/wheel/django/contrib/postgres
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uz/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/kab/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
copying build/lib/django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations
copying build/lib/django/contrib/redirects/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations
copying build/lib/django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations
copying build/lib/django/contrib/redirects/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects/migrations
copying build/lib/django/contrib/redirects/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects
copying build/lib/django/contrib/redirects/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects
copying build/lib/django/contrib/redirects/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects
copying build/lib/django/contrib/redirects/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects
copying build/lib/django/contrib/redirects/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/redirects
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uz/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/kab/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/base.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/cache.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/cached_db.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/db.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/file.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
copying build/lib/django/contrib/sessions/backends/signed_cookies.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/backends
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/management
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/management/commands
copying build/lib/django/contrib/sessions/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/management/commands
copying build/lib/django/contrib/sessions/management/commands/clearsessions.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/management/commands
copying build/lib/django/contrib/sessions/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/management
creating build/bdist.linux-x86_64/wheel/django/contrib/sessions/migrations
copying build/lib/django/contrib/sessions/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/migrations
copying build/lib/django/contrib/sessions/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions/migrations
copying build/lib/django/contrib/sessions/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions
copying build/lib/django/contrib/sessions/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions
copying build/lib/django/contrib/sessions/base_session.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions
copying build/lib/django/contrib/sessions/exceptions.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions
copying build/lib/django/contrib/sessions/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions
copying build/lib/django/contrib/sessions/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions
copying build/lib/django/contrib/sessions/serializers.py -> build/bdist.linux-x86_64/wheel/django/contrib/sessions
creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps
creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/templates
copying build/lib/django/contrib/sitemaps/templates/sitemap_index.xml -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/templates
copying build/lib/django/contrib/sitemaps/templates/sitemap.xml -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/templates
creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management
creating build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management/commands
copying build/lib/django/contrib/sitemaps/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management/commands
copying build/lib/django/contrib/sitemaps/management/commands/ping_google.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management/commands
copying build/lib/django/contrib/sitemaps/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps/management
copying build/lib/django/contrib/sitemaps/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps
copying build/lib/django/contrib/sitemaps/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps
copying build/lib/django/contrib/sitemaps/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/sitemaps
creating build/bdist.linux-x86_64/wheel/django/contrib/sites
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hant/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/zh_Hans/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/vi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uz/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ur/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/uk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/udm/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/th/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/tg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/te/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ta/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sw/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr_Latn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sq/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/sk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ru/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ro/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt_BR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/pa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/os/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ne/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/nb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/my/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ms/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ms/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ml/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/mk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lv/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lt/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/lb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ky/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ko/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/km/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kk/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/kab/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ka/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ja/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/it/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/is/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/io/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/id/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ia/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/hi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/he/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gl/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/gd/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ga/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fr/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fi/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/fa/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eu/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/et/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_VE/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_MX/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_CO/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es_AR/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/es/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/eo/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_GB/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en_AU/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/en/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/el/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/dsb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/de/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/da/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cy/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/cs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ckb/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ca/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bs/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/br/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bn/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/bg/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/be/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/az/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ast/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar_DZ/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/ar/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af/LC_MESSAGES
copying build/lib/django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/django/contrib/sites/locale/af/LC_MESSAGES
creating build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations
copying build/lib/django/contrib/sites/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations
copying build/lib/django/contrib/sites/migrations/0002_alter_domain_unique.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations
copying build/lib/django/contrib/sites/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites/migrations
copying build/lib/django/contrib/sites/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/admin.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/management.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/managers.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/middleware.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/models.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/requests.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
copying build/lib/django/contrib/sites/shortcuts.py -> build/bdist.linux-x86_64/wheel/django/contrib/sites
creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management
creating build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/collectstatic.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/findstatic.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/commands/runserver.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management/commands
copying build/lib/django/contrib/staticfiles/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles/management
copying build/lib/django/contrib/staticfiles/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/checks.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/finders.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/handlers.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/storage.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/testing.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/urls.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/utils.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
copying build/lib/django/contrib/staticfiles/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/staticfiles
creating build/bdist.linux-x86_64/wheel/django/contrib/syndication
copying build/lib/django/contrib/syndication/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib/syndication
copying build/lib/django/contrib/syndication/apps.py -> build/bdist.linux-x86_64/wheel/django/contrib/syndication
copying build/lib/django/contrib/syndication/views.py -> build/bdist.linux-x86_64/wheel/django/contrib/syndication
copying build/lib/django/contrib/__init__.py -> build/bdist.linux-x86_64/wheel/django/contrib
creating build/bdist.linux-x86_64/wheel/django/core
creating build/bdist.linux-x86_64/wheel/django/core/cache
creating build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/base.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/db.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/dummy.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/filebased.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/locmem.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/memcached.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/backends/redis.py -> build/bdist.linux-x86_64/wheel/django/core/cache/backends
copying build/lib/django/core/cache/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/cache
copying build/lib/django/core/cache/utils.py -> build/bdist.linux-x86_64/wheel/django/core/cache
creating build/bdist.linux-x86_64/wheel/django/core/checks
creating build/bdist.linux-x86_64/wheel/django/core/checks/compatibility
copying build/lib/django/core/checks/compatibility/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/checks/compatibility
copying build/lib/django/core/checks/compatibility/django_4_0.py -> build/bdist.linux-x86_64/wheel/django/core/checks/compatibility
creating build/bdist.linux-x86_64/wheel/django/core/checks/security
copying build/lib/django/core/checks/security/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security
copying build/lib/django/core/checks/security/base.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security
copying build/lib/django/core/checks/security/csrf.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security
copying build/lib/django/core/checks/security/sessions.py -> build/bdist.linux-x86_64/wheel/django/core/checks/security
copying build/lib/django/core/checks/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/async_checks.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/caches.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/database.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/files.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/messages.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/model_checks.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/registry.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/templates.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/translation.py -> build/bdist.linux-x86_64/wheel/django/core/checks
copying build/lib/django/core/checks/urls.py -> build/bdist.linux-x86_64/wheel/django/core/checks
creating build/bdist.linux-x86_64/wheel/django/core/files
creating build/bdist.linux-x86_64/wheel/django/core/files/storage
copying build/lib/django/core/files/storage/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage
copying build/lib/django/core/files/storage/base.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage
copying build/lib/django/core/files/storage/filesystem.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage
copying build/lib/django/core/files/storage/handler.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage
copying build/lib/django/core/files/storage/memory.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage
copying build/lib/django/core/files/storage/mixins.py -> build/bdist.linux-x86_64/wheel/django/core/files/storage
copying build/lib/django/core/files/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/base.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/images.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/locks.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/move.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/temp.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/uploadedfile.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/uploadhandler.py -> build/bdist.linux-x86_64/wheel/django/core/files
copying build/lib/django/core/files/utils.py -> build/bdist.linux-x86_64/wheel/django/core/files
creating build/bdist.linux-x86_64/wheel/django/core/handlers
copying build/lib/django/core/handlers/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/handlers
copying build/lib/django/core/handlers/asgi.py -> build/bdist.linux-x86_64/wheel/django/core/handlers
copying build/lib/django/core/handlers/base.py -> build/bdist.linux-x86_64/wheel/django/core/handlers
copying build/lib/django/core/handlers/exception.py -> build/bdist.linux-x86_64/wheel/django/core/handlers
copying build/lib/django/core/handlers/wsgi.py -> build/bdist.linux-x86_64/wheel/django/core/handlers
creating build/bdist.linux-x86_64/wheel/django/core/mail
creating build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/base.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/console.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/dummy.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/filebased.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/locmem.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/backends/smtp.py -> build/bdist.linux-x86_64/wheel/django/core/mail/backends
copying build/lib/django/core/mail/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/mail
copying build/lib/django/core/mail/message.py -> build/bdist.linux-x86_64/wheel/django/core/mail
copying build/lib/django/core/mail/utils.py -> build/bdist.linux-x86_64/wheel/django/core/mail
creating build/bdist.linux-x86_64/wheel/django/core/management
creating build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/check.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/compilemessages.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/createcachetable.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/dbshell.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/diffsettings.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/dumpdata.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/flush.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/inspectdb.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/loaddata.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/makemessages.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/makemigrations.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/migrate.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/optimizemigration.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/runserver.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/sendtestemail.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/shell.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/showmigrations.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/sqlflush.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/sqlmigrate.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/sqlsequencereset.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/squashmigrations.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/startapp.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/startproject.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/test.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/commands/testserver.py -> build/bdist.linux-x86_64/wheel/django/core/management/commands
copying build/lib/django/core/management/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/management
copying build/lib/django/core/management/base.py -> build/bdist.linux-x86_64/wheel/django/core/management
copying build/lib/django/core/management/color.py -> build/bdist.linux-x86_64/wheel/django/core/management
copying build/lib/django/core/management/sql.py -> build/bdist.linux-x86_64/wheel/django/core/management
copying build/lib/django/core/management/templates.py -> build/bdist.linux-x86_64/wheel/django/core/management
copying build/lib/django/core/management/utils.py -> build/bdist.linux-x86_64/wheel/django/core/management
creating build/bdist.linux-x86_64/wheel/django/core/serializers
copying build/lib/django/core/serializers/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/serializers
copying build/lib/django/core/serializers/base.py -> build/bdist.linux-x86_64/wheel/django/core/serializers
copying build/lib/django/core/serializers/json.py -> build/bdist.linux-x86_64/wheel/django/core/serializers
copying build/lib/django/core/serializers/jsonl.py -> build/bdist.linux-x86_64/wheel/django/core/serializers
copying build/lib/django/core/serializers/python.py -> build/bdist.linux-x86_64/wheel/django/core/serializers
copying build/lib/django/core/serializers/pyyaml.py -> build/bdist.linux-x86_64/wheel/django/core/serializers
copying build/lib/django/core/serializers/xml_serializer.py -> build/bdist.linux-x86_64/wheel/django/core/serializers
creating build/bdist.linux-x86_64/wheel/django/core/servers
copying build/lib/django/core/servers/__init__.py -> build/bdist.linux-x86_64/wheel/django/core/servers
copying build/lib/django/core/servers/basehttp.py -> build/bdist.linux-x86_64/wheel/django/core/servers
copying build/lib/django/core/__init__.py -> build/bdist.linux-x86_64/wheel/django/core
copying build/lib/django/core/asgi.py -> build/bdist.linux-x86_64/wheel/django/core
copying build/lib/django/core/exceptions.py -> build/bdist.linux-x86_64/wheel/django/core
copying build/lib/django/core/paginator.py -> build/bdist.linux-x86_64/wheel/django/core
copying build/lib/django/core/signals.py -> build/bdist.linux-x86_64/wheel/django/core
copying build/lib/django/core/signing.py -> build/bdist.linux-x86_64/wheel/django/core
copying build/lib/django/core/validators.py -> build/bdist.linux-x86_64/wheel/django/core
copying build/lib/django/core/wsgi.py -> build/bdist.linux-x86_64/wheel/django/core
creating build/bdist.linux-x86_64/wheel/django/db
creating build/bdist.linux-x86_64/wheel/django/db/backends
creating build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
copying build/lib/django/db/backends/base/validation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/base
creating build/bdist.linux-x86_64/wheel/django/db/backends/dummy
copying build/lib/django/db/backends/dummy/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/dummy
copying build/lib/django/db/backends/dummy/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/dummy
copying build/lib/django/db/backends/dummy/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/dummy
creating build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/compiler.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
copying build/lib/django/db/backends/mysql/validation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/mysql
creating build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/functions.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/utils.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
copying build/lib/django/db/backends/oracle/validation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/oracle
creating build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/psycopg_any.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
copying build/lib/django/db/backends/postgresql/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/postgresql
creating build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/_functions.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/base.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/client.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/creation.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/features.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/introspection.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/operations.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/sqlite3/schema.py -> build/bdist.linux-x86_64/wheel/django/db/backends/sqlite3
copying build/lib/django/db/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/backends
copying build/lib/django/db/backends/ddl_references.py -> build/bdist.linux-x86_64/wheel/django/db/backends
copying build/lib/django/db/backends/signals.py -> build/bdist.linux-x86_64/wheel/django/db/backends
copying build/lib/django/db/backends/utils.py -> build/bdist.linux-x86_64/wheel/django/db/backends
creating build/bdist.linux-x86_64/wheel/django/db/migrations
creating build/bdist.linux-x86_64/wheel/django/db/migrations/operations
copying build/lib/django/db/migrations/operations/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations
copying build/lib/django/db/migrations/operations/base.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations
copying build/lib/django/db/migrations/operations/fields.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations
copying build/lib/django/db/migrations/operations/models.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations
copying build/lib/django/db/migrations/operations/special.py -> build/bdist.linux-x86_64/wheel/django/db/migrations/operations
copying build/lib/django/db/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/autodetector.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/exceptions.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/executor.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/graph.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/loader.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/migration.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/optimizer.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/questioner.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/recorder.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/serializer.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/state.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/utils.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
copying build/lib/django/db/migrations/writer.py -> build/bdist.linux-x86_64/wheel/django/db/migrations
creating build/bdist.linux-x86_64/wheel/django/db/models
creating build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/files.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/json.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/mixins.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/proxy.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/related.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/related_descriptors.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/related_lookups.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
copying build/lib/django/db/models/fields/reverse_related.py -> build/bdist.linux-x86_64/wheel/django/db/models/fields
creating build/bdist.linux-x86_64/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/comparison.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/datetime.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/math.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/mixins.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/text.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions
copying build/lib/django/db/models/functions/window.py -> build/bdist.linux-x86_64/wheel/django/db/models/functions
creating build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/compiler.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/constants.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/datastructures.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/query.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/subqueries.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/sql/where.py -> build/bdist.linux-x86_64/wheel/django/db/models/sql
copying build/lib/django/db/models/__init__.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/aggregates.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/base.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/constants.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/constraints.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/deletion.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/enums.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/expressions.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/indexes.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/lookups.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/manager.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/options.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/query.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/query_utils.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/signals.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/models/utils.py -> build/bdist.linux-x86_64/wheel/django/db/models
copying build/lib/django/db/__init__.py -> build/bdist.linux-x86_64/wheel/django/db
copying build/lib/django/db/transaction.py -> build/bdist.linux-x86_64/wheel/django/db
copying build/lib/django/db/utils.py -> build/bdist.linux-x86_64/wheel/django/db
creating build/bdist.linux-x86_64/wheel/django/dispatch
copying build/lib/django/dispatch/license.txt -> build/bdist.linux-x86_64/wheel/django/dispatch
copying build/lib/django/dispatch/__init__.py -> build/bdist.linux-x86_64/wheel/django/dispatch
copying build/lib/django/dispatch/dispatcher.py -> build/bdist.linux-x86_64/wheel/django/dispatch
creating build/bdist.linux-x86_64/wheel/django/forms
creating build/bdist.linux-x86_64/wheel/django/forms/templates
creating build/bdist.linux-x86_64/wheel/django/forms/templates/django
creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/url.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/time.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/textarea.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/text.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/splitdatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/select_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/select_date.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/select.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/radio_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/radio.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/password.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/number.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/multiwidget.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/multiple_input.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/input_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/input.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/file.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/email.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/datetime.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/date.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/checkbox_select.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/checkbox_option.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/checkbox.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
copying build/lib/django/forms/templates/django/forms/widgets/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/widgets
creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets
copying build/lib/django/forms/templates/django/forms/formsets/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets
copying build/lib/django/forms/templates/django/forms/formsets/table.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets
copying build/lib/django/forms/templates/django/forms/formsets/p.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets
copying build/lib/django/forms/templates/django/forms/formsets/div.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets
copying build/lib/django/forms/templates/django/forms/formsets/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/formsets
creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors
creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list
copying build/lib/django/forms/templates/django/forms/errors/list/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list
copying build/lib/django/forms/templates/django/forms/errors/list/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list
copying build/lib/django/forms/templates/django/forms/errors/list/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/list
creating build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict
copying build/lib/django/forms/templates/django/forms/errors/dict/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict
copying build/lib/django/forms/templates/django/forms/errors/dict/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict
copying build/lib/django/forms/templates/django/forms/errors/dict/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms/errors/dict
copying build/lib/django/forms/templates/django/forms/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
copying build/lib/django/forms/templates/django/forms/table.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
copying build/lib/django/forms/templates/django/forms/p.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
copying build/lib/django/forms/templates/django/forms/label.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
copying build/lib/django/forms/templates/django/forms/div.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
copying build/lib/django/forms/templates/django/forms/default.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
copying build/lib/django/forms/templates/django/forms/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/templates/django/forms
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/url.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/time.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/textarea.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/text.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/splitdatetime.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/select_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/select_date.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/select.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/radio_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/radio.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/password.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/number.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/multiwidget.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_input.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/input_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/input.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/hidden.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/file.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/email.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/datetime.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/date.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_select.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox_option.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/checkbox.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
copying build/lib/django/forms/jinja2/django/forms/widgets/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/widgets
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets
copying build/lib/django/forms/jinja2/django/forms/formsets/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets
copying build/lib/django/forms/jinja2/django/forms/formsets/table.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets
copying build/lib/django/forms/jinja2/django/forms/formsets/p.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets
copying build/lib/django/forms/jinja2/django/forms/formsets/div.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets
copying build/lib/django/forms/jinja2/django/forms/formsets/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/formsets
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list
copying build/lib/django/forms/jinja2/django/forms/errors/list/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list
copying build/lib/django/forms/jinja2/django/forms/errors/list/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list
copying build/lib/django/forms/jinja2/django/forms/errors/list/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/list
creating build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict
copying build/lib/django/forms/jinja2/django/forms/errors/dict/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict
copying build/lib/django/forms/jinja2/django/forms/errors/dict/text.txt -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict
copying build/lib/django/forms/jinja2/django/forms/errors/dict/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms/errors/dict
copying build/lib/django/forms/jinja2/django/forms/ul.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
copying build/lib/django/forms/jinja2/django/forms/table.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
copying build/lib/django/forms/jinja2/django/forms/p.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
copying build/lib/django/forms/jinja2/django/forms/label.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
copying build/lib/django/forms/jinja2/django/forms/div.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
copying build/lib/django/forms/jinja2/django/forms/default.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
copying build/lib/django/forms/jinja2/django/forms/attrs.html -> build/bdist.linux-x86_64/wheel/django/forms/jinja2/django/forms
copying build/lib/django/forms/__init__.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/boundfield.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/fields.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/forms.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/formsets.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/models.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/renderers.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/utils.py -> build/bdist.linux-x86_64/wheel/django/forms
copying build/lib/django/forms/widgets.py -> build/bdist.linux-x86_64/wheel/django/forms
creating build/bdist.linux-x86_64/wheel/django/http
copying build/lib/django/http/__init__.py -> build/bdist.linux-x86_64/wheel/django/http
copying build/lib/django/http/cookie.py -> build/bdist.linux-x86_64/wheel/django/http
copying build/lib/django/http/multipartparser.py -> build/bdist.linux-x86_64/wheel/django/http
copying build/lib/django/http/request.py -> build/bdist.linux-x86_64/wheel/django/http
copying build/lib/django/http/response.py -> build/bdist.linux-x86_64/wheel/django/http
creating build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/__init__.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/cache.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/clickjacking.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/common.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/csrf.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/gzip.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/http.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/locale.py -> build/bdist.linux-x86_64/wheel/django/middleware
copying build/lib/django/middleware/security.py -> build/bdist.linux-x86_64/wheel/django/middleware
creating build/bdist.linux-x86_64/wheel/django/template
creating build/bdist.linux-x86_64/wheel/django/template/backends
copying build/lib/django/template/backends/__init__.py -> build/bdist.linux-x86_64/wheel/django/template/backends
copying build/lib/django/template/backends/base.py -> build/bdist.linux-x86_64/wheel/django/template/backends
copying build/lib/django/template/backends/django.py -> build/bdist.linux-x86_64/wheel/django/template/backends
copying build/lib/django/template/backends/dummy.py -> build/bdist.linux-x86_64/wheel/django/template/backends
copying build/lib/django/template/backends/jinja2.py -> build/bdist.linux-x86_64/wheel/django/template/backends
copying build/lib/django/template/backends/utils.py -> build/bdist.linux-x86_64/wheel/django/template/backends
creating build/bdist.linux-x86_64/wheel/django/template/loaders
copying build/lib/django/template/loaders/__init__.py -> build/bdist.linux-x86_64/wheel/django/template/loaders
copying build/lib/django/template/loaders/app_directories.py -> build/bdist.linux-x86_64/wheel/django/template/loaders
copying build/lib/django/template/loaders/base.py -> build/bdist.linux-x86_64/wheel/django/template/loaders
copying build/lib/django/template/loaders/cached.py -> build/bdist.linux-x86_64/wheel/django/template/loaders
copying build/lib/django/template/loaders/filesystem.py -> build/bdist.linux-x86_64/wheel/django/template/loaders
copying build/lib/django/template/loaders/locmem.py -> build/bdist.linux-x86_64/wheel/django/template/loaders
copying build/lib/django/template/__init__.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/autoreload.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/base.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/context.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/context_processors.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/defaultfilters.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/defaulttags.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/engine.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/exceptions.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/library.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/loader.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/loader_tags.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/response.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/smartif.py -> build/bdist.linux-x86_64/wheel/django/template
copying build/lib/django/template/utils.py -> build/bdist.linux-x86_64/wheel/django/template
creating build/bdist.linux-x86_64/wheel/django/templatetags
copying build/lib/django/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/django/templatetags
copying build/lib/django/templatetags/cache.py -> build/bdist.linux-x86_64/wheel/django/templatetags
copying build/lib/django/templatetags/i18n.py -> build/bdist.linux-x86_64/wheel/django/templatetags
copying build/lib/django/templatetags/l10n.py -> build/bdist.linux-x86_64/wheel/django/templatetags
copying build/lib/django/templatetags/static.py -> build/bdist.linux-x86_64/wheel/django/templatetags
copying build/lib/django/templatetags/tz.py -> build/bdist.linux-x86_64/wheel/django/templatetags
creating build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/__init__.py -> build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/client.py -> build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/html.py -> build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/runner.py -> build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/selenium.py -> build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/signals.py -> build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/testcases.py -> build/bdist.linux-x86_64/wheel/django/test
copying build/lib/django/test/utils.py -> build/bdist.linux-x86_64/wheel/django/test
creating build/bdist.linux-x86_64/wheel/django/urls
copying build/lib/django/urls/__init__.py -> build/bdist.linux-x86_64/wheel/django/urls
copying build/lib/django/urls/base.py -> build/bdist.linux-x86_64/wheel/django/urls
copying build/lib/django/urls/conf.py -> build/bdist.linux-x86_64/wheel/django/urls
copying build/lib/django/urls/converters.py -> build/bdist.linux-x86_64/wheel/django/urls
copying build/lib/django/urls/exceptions.py -> build/bdist.linux-x86_64/wheel/django/urls
copying build/lib/django/urls/resolvers.py -> build/bdist.linux-x86_64/wheel/django/urls
copying build/lib/django/urls/utils.py -> build/bdist.linux-x86_64/wheel/django/urls
creating build/bdist.linux-x86_64/wheel/django/utils
creating build/bdist.linux-x86_64/wheel/django/utils/translation
copying build/lib/django/utils/translation/__init__.py -> build/bdist.linux-x86_64/wheel/django/utils/translation
copying build/lib/django/utils/translation/reloader.py -> build/bdist.linux-x86_64/wheel/django/utils/translation
copying build/lib/django/utils/translation/template.py -> build/bdist.linux-x86_64/wheel/django/utils/translation
copying build/lib/django/utils/translation/trans_null.py -> build/bdist.linux-x86_64/wheel/django/utils/translation
copying build/lib/django/utils/translation/trans_real.py -> build/bdist.linux-x86_64/wheel/django/utils/translation
copying build/lib/django/utils/__init__.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/_os.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/archive.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/asyncio.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/autoreload.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/baseconv.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/cache.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/connection.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/crypto.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/datastructures.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/dateformat.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/dateparse.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/dates.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/datetime_safe.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/deconstruct.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/decorators.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/deprecation.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/duration.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/encoding.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/feedgenerator.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/formats.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/functional.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/hashable.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/html.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/http.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/inspect.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/ipv6.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/itercompat.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/jslex.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/log.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/lorem_ipsum.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/module_loading.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/numberformat.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/regex_helper.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/safestring.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/termcolors.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/text.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/timesince.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/timezone.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/topological_sort.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/tree.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/version.py -> build/bdist.linux-x86_64/wheel/django/utils
copying build/lib/django/utils/xmlutils.py -> build/bdist.linux-x86_64/wheel/django/utils
creating build/bdist.linux-x86_64/wheel/django/views
creating build/bdist.linux-x86_64/wheel/django/views/templates
copying build/lib/django/views/templates/technical_500.txt -> build/bdist.linux-x86_64/wheel/django/views/templates
copying build/lib/django/views/templates/technical_500.html -> build/bdist.linux-x86_64/wheel/django/views/templates
copying build/lib/django/views/templates/technical_404.html -> build/bdist.linux-x86_64/wheel/django/views/templates
copying build/lib/django/views/templates/default_urlconf.html -> build/bdist.linux-x86_64/wheel/django/views/templates
creating build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/__init__.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/cache.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/clickjacking.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/common.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/csrf.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/debug.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/gzip.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/http.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
copying build/lib/django/views/decorators/vary.py -> build/bdist.linux-x86_64/wheel/django/views/decorators
creating build/bdist.linux-x86_64/wheel/django/views/generic
copying build/lib/django/views/generic/__init__.py -> build/bdist.linux-x86_64/wheel/django/views/generic
copying build/lib/django/views/generic/base.py -> build/bdist.linux-x86_64/wheel/django/views/generic
copying build/lib/django/views/generic/dates.py -> build/bdist.linux-x86_64/wheel/django/views/generic
copying build/lib/django/views/generic/detail.py -> build/bdist.linux-x86_64/wheel/django/views/generic
copying build/lib/django/views/generic/edit.py -> build/bdist.linux-x86_64/wheel/django/views/generic
copying build/lib/django/views/generic/list.py -> build/bdist.linux-x86_64/wheel/django/views/generic
copying build/lib/django/views/__init__.py -> build/bdist.linux-x86_64/wheel/django/views
copying build/lib/django/views/csrf.py -> build/bdist.linux-x86_64/wheel/django/views
copying build/lib/django/views/debug.py -> build/bdist.linux-x86_64/wheel/django/views
copying build/lib/django/views/defaults.py -> build/bdist.linux-x86_64/wheel/django/views
copying build/lib/django/views/i18n.py -> build/bdist.linux-x86_64/wheel/django/views
copying build/lib/django/views/static.py -> build/bdist.linux-x86_64/wheel/django/views
copying build/lib/django/__init__.py -> build/bdist.linux-x86_64/wheel/django
copying build/lib/django/__main__.py -> build/bdist.linux-x86_64/wheel/django
copying build/lib/django/shortcuts.py -> build/bdist.linux-x86_64/wheel/django
running install_egg_info
Copying Django.egg-info to build/bdist.linux-x86_64/wheel/Django-4.2.3-py3.12.egg-info
running install_scripts
creating build/bdist.linux-x86_64/wheel/Django-4.2.3.dist-info/WHEEL
creating '/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir/pip-wheel-xpj92hea/.tmp-4n4et5yg/Django-4.2.3-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
adding 'django/__init__.py'
adding 'django/__main__.py'
adding 'django/shortcuts.py'
adding 'django/apps/__init__.py'
adding 'django/apps/config.py'
adding 'django/apps/registry.py'
adding 'django/conf/__init__.py'
adding 'django/conf/global_settings.py'
adding 'django/conf/app_template/__init__.py-tpl'
adding 'django/conf/app_template/admin.py-tpl'
adding 'django/conf/app_template/apps.py-tpl'
adding 'django/conf/app_template/models.py-tpl'
adding 'django/conf/app_template/tests.py-tpl'
adding 'django/conf/app_template/views.py-tpl'
adding 'django/conf/app_template/migrations/__init__.py-tpl'
adding 'django/conf/locale/__init__.py'
adding 'django/conf/locale/af/LC_MESSAGES/django.mo'
adding 'django/conf/locale/af/LC_MESSAGES/django.po'
adding 'django/conf/locale/ar/__init__.py'
adding 'django/conf/locale/ar/formats.py'
adding 'django/conf/locale/ar/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ar/LC_MESSAGES/django.po'
adding 'django/conf/locale/ar_DZ/__init__.py'
adding 'django/conf/locale/ar_DZ/formats.py'
adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/conf/locale/ast/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ast/LC_MESSAGES/django.po'
adding 'django/conf/locale/az/__init__.py'
adding 'django/conf/locale/az/formats.py'
adding 'django/conf/locale/az/LC_MESSAGES/django.mo'
adding 'django/conf/locale/az/LC_MESSAGES/django.po'
adding 'django/conf/locale/be/LC_MESSAGES/django.mo'
adding 'django/conf/locale/be/LC_MESSAGES/django.po'
adding 'django/conf/locale/bg/__init__.py'
adding 'django/conf/locale/bg/formats.py'
adding 'django/conf/locale/bg/LC_MESSAGES/django.mo'
adding 'django/conf/locale/bg/LC_MESSAGES/django.po'
adding 'django/conf/locale/bn/__init__.py'
adding 'django/conf/locale/bn/formats.py'
adding 'django/conf/locale/bn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/bn/LC_MESSAGES/django.po'
adding 'django/conf/locale/br/LC_MESSAGES/django.mo'
adding 'django/conf/locale/br/LC_MESSAGES/django.po'
adding 'django/conf/locale/bs/__init__.py'
adding 'django/conf/locale/bs/formats.py'
adding 'django/conf/locale/bs/LC_MESSAGES/django.mo'
adding 'django/conf/locale/bs/LC_MESSAGES/django.po'
adding 'django/conf/locale/ca/__init__.py'
adding 'django/conf/locale/ca/formats.py'
adding 'django/conf/locale/ca/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ca/LC_MESSAGES/django.po'
adding 'django/conf/locale/ckb/__init__.py'
adding 'django/conf/locale/ckb/formats.py'
adding 'django/conf/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ckb/LC_MESSAGES/django.po'
adding 'django/conf/locale/cs/__init__.py'
adding 'django/conf/locale/cs/formats.py'
adding 'django/conf/locale/cs/LC_MESSAGES/django.mo'
adding 'django/conf/locale/cs/LC_MESSAGES/django.po'
adding 'django/conf/locale/cy/__init__.py'
adding 'django/conf/locale/cy/formats.py'
adding 'django/conf/locale/cy/LC_MESSAGES/django.mo'
adding 'django/conf/locale/cy/LC_MESSAGES/django.po'
adding 'django/conf/locale/da/__init__.py'
adding 'django/conf/locale/da/formats.py'
adding 'django/conf/locale/da/LC_MESSAGES/django.mo'
adding 'django/conf/locale/da/LC_MESSAGES/django.po'
adding 'django/conf/locale/de/__init__.py'
adding 'django/conf/locale/de/formats.py'
adding 'django/conf/locale/de/LC_MESSAGES/django.mo'
adding 'django/conf/locale/de/LC_MESSAGES/django.po'
adding 'django/conf/locale/de_CH/__init__.py'
adding 'django/conf/locale/de_CH/formats.py'
adding 'django/conf/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/dsb/LC_MESSAGES/django.po'
adding 'django/conf/locale/el/__init__.py'
adding 'django/conf/locale/el/formats.py'
adding 'django/conf/locale/el/LC_MESSAGES/django.mo'
adding 'django/conf/locale/el/LC_MESSAGES/django.po'
adding 'django/conf/locale/en/__init__.py'
adding 'django/conf/locale/en/formats.py'
adding 'django/conf/locale/en/LC_MESSAGES/django.mo'
adding 'django/conf/locale/en/LC_MESSAGES/django.po'
adding 'django/conf/locale/en_AU/__init__.py'
adding 'django/conf/locale/en_AU/formats.py'
adding 'django/conf/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/conf/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/conf/locale/en_GB/__init__.py'
adding 'django/conf/locale/en_GB/formats.py'
adding 'django/conf/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/conf/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/conf/locale/eo/__init__.py'
adding 'django/conf/locale/eo/formats.py'
adding 'django/conf/locale/eo/LC_MESSAGES/django.mo'
adding 'django/conf/locale/eo/LC_MESSAGES/django.po'
adding 'django/conf/locale/es/__init__.py'
adding 'django/conf/locale/es/formats.py'
adding 'django/conf/locale/es/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_AR/__init__.py'
adding 'django/conf/locale/es_AR/formats.py'
adding 'django/conf/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_CO/__init__.py'
adding 'django/conf/locale/es_CO/formats.py'
adding 'django/conf/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_MX/__init__.py'
adding 'django/conf/locale/es_MX/formats.py'
adding 'django/conf/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/conf/locale/es_NI/__init__.py'
adding 'django/conf/locale/es_NI/formats.py'
adding 'django/conf/locale/es_PR/__init__.py'
adding 'django/conf/locale/es_PR/formats.py'
adding 'django/conf/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/conf/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/conf/locale/et/__init__.py'
adding 'django/conf/locale/et/formats.py'
adding 'django/conf/locale/et/LC_MESSAGES/django.mo'
adding 'django/conf/locale/et/LC_MESSAGES/django.po'
adding 'django/conf/locale/eu/__init__.py'
adding 'django/conf/locale/eu/formats.py'
adding 'django/conf/locale/eu/LC_MESSAGES/django.mo'
adding 'django/conf/locale/eu/LC_MESSAGES/django.po'
adding 'django/conf/locale/fa/__init__.py'
adding 'django/conf/locale/fa/formats.py'
adding 'django/conf/locale/fa/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fa/LC_MESSAGES/django.po'
adding 'django/conf/locale/fi/__init__.py'
adding 'django/conf/locale/fi/formats.py'
adding 'django/conf/locale/fi/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fi/LC_MESSAGES/django.po'
adding 'django/conf/locale/fr/__init__.py'
adding 'django/conf/locale/fr/formats.py'
adding 'django/conf/locale/fr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fr/LC_MESSAGES/django.po'
adding 'django/conf/locale/fy/__init__.py'
adding 'django/conf/locale/fy/formats.py'
adding 'django/conf/locale/fy/LC_MESSAGES/django.mo'
adding 'django/conf/locale/fy/LC_MESSAGES/django.po'
adding 'django/conf/locale/ga/__init__.py'
adding 'django/conf/locale/ga/formats.py'
adding 'django/conf/locale/ga/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ga/LC_MESSAGES/django.po'
adding 'django/conf/locale/gd/__init__.py'
adding 'django/conf/locale/gd/formats.py'
adding 'django/conf/locale/gd/LC_MESSAGES/django.mo'
adding 'django/conf/locale/gd/LC_MESSAGES/django.po'
adding 'django/conf/locale/gl/__init__.py'
adding 'django/conf/locale/gl/formats.py'
adding 'django/conf/locale/gl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/gl/LC_MESSAGES/django.po'
adding 'django/conf/locale/he/__init__.py'
adding 'django/conf/locale/he/formats.py'
adding 'django/conf/locale/he/LC_MESSAGES/django.mo'
adding 'django/conf/locale/he/LC_MESSAGES/django.po'
adding 'django/conf/locale/hi/__init__.py'
adding 'django/conf/locale/hi/formats.py'
adding 'django/conf/locale/hi/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hi/LC_MESSAGES/django.po'
adding 'django/conf/locale/hr/__init__.py'
adding 'django/conf/locale/hr/formats.py'
adding 'django/conf/locale/hr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hr/LC_MESSAGES/django.po'
adding 'django/conf/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hsb/LC_MESSAGES/django.po'
adding 'django/conf/locale/hu/__init__.py'
adding 'django/conf/locale/hu/formats.py'
adding 'django/conf/locale/hu/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hu/LC_MESSAGES/django.po'
adding 'django/conf/locale/hy/LC_MESSAGES/django.mo'
adding 'django/conf/locale/hy/LC_MESSAGES/django.po'
adding 'django/conf/locale/ia/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ia/LC_MESSAGES/django.po'
adding 'django/conf/locale/id/__init__.py'
adding 'django/conf/locale/id/formats.py'
adding 'django/conf/locale/id/LC_MESSAGES/django.mo'
adding 'django/conf/locale/id/LC_MESSAGES/django.po'
adding 'django/conf/locale/ig/__init__.py'
adding 'django/conf/locale/ig/formats.py'
adding 'django/conf/locale/ig/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ig/LC_MESSAGES/django.po'
adding 'django/conf/locale/io/LC_MESSAGES/django.mo'
adding 'django/conf/locale/io/LC_MESSAGES/django.po'
adding 'django/conf/locale/is/__init__.py'
adding 'django/conf/locale/is/formats.py'
adding 'django/conf/locale/is/LC_MESSAGES/django.mo'
adding 'django/conf/locale/is/LC_MESSAGES/django.po'
adding 'django/conf/locale/it/__init__.py'
adding 'django/conf/locale/it/formats.py'
adding 'django/conf/locale/it/LC_MESSAGES/django.mo'
adding 'django/conf/locale/it/LC_MESSAGES/django.po'
adding 'django/conf/locale/ja/__init__.py'
adding 'django/conf/locale/ja/formats.py'
adding 'django/conf/locale/ja/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ja/LC_MESSAGES/django.po'
adding 'django/conf/locale/ka/__init__.py'
adding 'django/conf/locale/ka/formats.py'
adding 'django/conf/locale/ka/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ka/LC_MESSAGES/django.po'
adding 'django/conf/locale/kab/LC_MESSAGES/django.mo'
adding 'django/conf/locale/kab/LC_MESSAGES/django.po'
adding 'django/conf/locale/kk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/kk/LC_MESSAGES/django.po'
adding 'django/conf/locale/km/__init__.py'
adding 'django/conf/locale/km/formats.py'
adding 'django/conf/locale/km/LC_MESSAGES/django.mo'
adding 'django/conf/locale/km/LC_MESSAGES/django.po'
adding 'django/conf/locale/kn/__init__.py'
adding 'django/conf/locale/kn/formats.py'
adding 'django/conf/locale/kn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/kn/LC_MESSAGES/django.po'
adding 'django/conf/locale/ko/__init__.py'
adding 'django/conf/locale/ko/formats.py'
adding 'django/conf/locale/ko/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ko/LC_MESSAGES/django.po'
adding 'django/conf/locale/ky/__init__.py'
adding 'django/conf/locale/ky/formats.py'
adding 'django/conf/locale/ky/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ky/LC_MESSAGES/django.po'
adding 'django/conf/locale/lb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/lb/LC_MESSAGES/django.po'
adding 'django/conf/locale/lt/__init__.py'
adding 'django/conf/locale/lt/formats.py'
adding 'django/conf/locale/lt/LC_MESSAGES/django.mo'
adding 'django/conf/locale/lt/LC_MESSAGES/django.po'
adding 'django/conf/locale/lv/__init__.py'
adding 'django/conf/locale/lv/formats.py'
adding 'django/conf/locale/lv/LC_MESSAGES/django.mo'
adding 'django/conf/locale/lv/LC_MESSAGES/django.po'
adding 'django/conf/locale/mk/__init__.py'
adding 'django/conf/locale/mk/formats.py'
adding 'django/conf/locale/mk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/mk/LC_MESSAGES/django.po'
adding 'django/conf/locale/ml/__init__.py'
adding 'django/conf/locale/ml/formats.py'
adding 'django/conf/locale/ml/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ml/LC_MESSAGES/django.po'
adding 'django/conf/locale/mn/__init__.py'
adding 'django/conf/locale/mn/formats.py'
adding 'django/conf/locale/mn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/mn/LC_MESSAGES/django.po'
adding 'django/conf/locale/mr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/mr/LC_MESSAGES/django.po'
adding 'django/conf/locale/ms/__init__.py'
adding 'django/conf/locale/ms/formats.py'
adding 'django/conf/locale/ms/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ms/LC_MESSAGES/django.po'
adding 'django/conf/locale/my/LC_MESSAGES/django.mo'
adding 'django/conf/locale/my/LC_MESSAGES/django.po'
adding 'django/conf/locale/nb/__init__.py'
adding 'django/conf/locale/nb/formats.py'
adding 'django/conf/locale/nb/LC_MESSAGES/django.mo'
adding 'django/conf/locale/nb/LC_MESSAGES/django.po'
adding 'django/conf/locale/ne/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ne/LC_MESSAGES/django.po'
adding 'django/conf/locale/nl/__init__.py'
adding 'django/conf/locale/nl/formats.py'
adding 'django/conf/locale/nl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/nl/LC_MESSAGES/django.po'
adding 'django/conf/locale/nn/__init__.py'
adding 'django/conf/locale/nn/formats.py'
adding 'django/conf/locale/nn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/nn/LC_MESSAGES/django.po'
adding 'django/conf/locale/os/LC_MESSAGES/django.mo'
adding 'django/conf/locale/os/LC_MESSAGES/django.po'
adding 'django/conf/locale/pa/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pa/LC_MESSAGES/django.po'
adding 'django/conf/locale/pl/__init__.py'
adding 'django/conf/locale/pl/formats.py'
adding 'django/conf/locale/pl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pl/LC_MESSAGES/django.po'
adding 'django/conf/locale/pt/__init__.py'
adding 'django/conf/locale/pt/formats.py'
adding 'django/conf/locale/pt/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pt/LC_MESSAGES/django.po'
adding 'django/conf/locale/pt_BR/__init__.py'
adding 'django/conf/locale/pt_BR/formats.py'
adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/conf/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/conf/locale/ro/__init__.py'
adding 'django/conf/locale/ro/formats.py'
adding 'django/conf/locale/ro/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ro/LC_MESSAGES/django.po'
adding 'django/conf/locale/ru/__init__.py'
adding 'django/conf/locale/ru/formats.py'
adding 'django/conf/locale/ru/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ru/LC_MESSAGES/django.po'
adding 'django/conf/locale/sk/__init__.py'
adding 'django/conf/locale/sk/formats.py'
adding 'django/conf/locale/sk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sk/LC_MESSAGES/django.po'
adding 'django/conf/locale/sl/__init__.py'
adding 'django/conf/locale/sl/formats.py'
adding 'django/conf/locale/sl/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sl/LC_MESSAGES/django.po'
adding 'django/conf/locale/sq/__init__.py'
adding 'django/conf/locale/sq/formats.py'
adding 'django/conf/locale/sq/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sq/LC_MESSAGES/django.po'
adding 'django/conf/locale/sr/__init__.py'
adding 'django/conf/locale/sr/formats.py'
adding 'django/conf/locale/sr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sr/LC_MESSAGES/django.po'
adding 'django/conf/locale/sr_Latn/__init__.py'
adding 'django/conf/locale/sr_Latn/formats.py'
adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/conf/locale/sv/__init__.py'
adding 'django/conf/locale/sv/formats.py'
adding 'django/conf/locale/sv/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sv/LC_MESSAGES/django.po'
adding 'django/conf/locale/sw/LC_MESSAGES/django.mo'
adding 'django/conf/locale/sw/LC_MESSAGES/django.po'
adding 'django/conf/locale/ta/__init__.py'
adding 'django/conf/locale/ta/formats.py'
adding 'django/conf/locale/ta/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ta/LC_MESSAGES/django.po'
adding 'django/conf/locale/te/__init__.py'
adding 'django/conf/locale/te/formats.py'
adding 'django/conf/locale/te/LC_MESSAGES/django.mo'
adding 'django/conf/locale/te/LC_MESSAGES/django.po'
adding 'django/conf/locale/tg/__init__.py'
adding 'django/conf/locale/tg/formats.py'
adding 'django/conf/locale/tg/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tg/LC_MESSAGES/django.po'
adding 'django/conf/locale/th/__init__.py'
adding 'django/conf/locale/th/formats.py'
adding 'django/conf/locale/th/LC_MESSAGES/django.mo'
adding 'django/conf/locale/th/LC_MESSAGES/django.po'
adding 'django/conf/locale/tk/__init__.py'
adding 'django/conf/locale/tk/formats.py'
adding 'django/conf/locale/tk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tk/LC_MESSAGES/django.po'
adding 'django/conf/locale/tr/__init__.py'
adding 'django/conf/locale/tr/formats.py'
adding 'django/conf/locale/tr/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tr/LC_MESSAGES/django.po'
adding 'django/conf/locale/tt/LC_MESSAGES/django.mo'
adding 'django/conf/locale/tt/LC_MESSAGES/django.po'
adding 'django/conf/locale/udm/LC_MESSAGES/django.mo'
adding 'django/conf/locale/udm/LC_MESSAGES/django.po'
adding 'django/conf/locale/uk/__init__.py'
adding 'django/conf/locale/uk/formats.py'
adding 'django/conf/locale/uk/LC_MESSAGES/django.mo'
adding 'django/conf/locale/uk/LC_MESSAGES/django.po'
adding 'django/conf/locale/ur/LC_MESSAGES/django.mo'
adding 'django/conf/locale/ur/LC_MESSAGES/django.po'
adding 'django/conf/locale/uz/__init__.py'
adding 'django/conf/locale/uz/formats.py'
adding 'django/conf/locale/uz/LC_MESSAGES/django.mo'
adding 'django/conf/locale/uz/LC_MESSAGES/django.po'
adding 'django/conf/locale/vi/__init__.py'
adding 'django/conf/locale/vi/formats.py'
adding 'django/conf/locale/vi/LC_MESSAGES/django.mo'
adding 'django/conf/locale/vi/LC_MESSAGES/django.po'
adding 'django/conf/locale/zh_Hans/__init__.py'
adding 'django/conf/locale/zh_Hans/formats.py'
adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/conf/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/conf/locale/zh_Hant/__init__.py'
adding 'django/conf/locale/zh_Hant/formats.py'
adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/conf/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/conf/project_template/manage.py-tpl'
adding 'django/conf/project_template/project_name/__init__.py-tpl'
adding 'django/conf/project_template/project_name/asgi.py-tpl'
adding 'django/conf/project_template/project_name/settings.py-tpl'
adding 'django/conf/project_template/project_name/urls.py-tpl'
adding 'django/conf/project_template/project_name/wsgi.py-tpl'
adding 'django/conf/urls/__init__.py'
adding 'django/conf/urls/i18n.py'
adding 'django/conf/urls/static.py'
adding 'django/contrib/__init__.py'
adding 'django/contrib/admin/__init__.py'
adding 'django/contrib/admin/actions.py'
adding 'django/contrib/admin/apps.py'
adding 'django/contrib/admin/checks.py'
adding 'django/contrib/admin/decorators.py'
adding 'django/contrib/admin/exceptions.py'
adding 'django/contrib/admin/filters.py'
adding 'django/contrib/admin/forms.py'
adding 'django/contrib/admin/helpers.py'
adding 'django/contrib/admin/models.py'
adding 'django/contrib/admin/options.py'
adding 'django/contrib/admin/sites.py'
adding 'django/contrib/admin/tests.py'
adding 'django/contrib/admin/utils.py'
adding 'django/contrib/admin/widgets.py'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/am/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ckb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ms/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo'
adding 'django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po'
adding 'django/contrib/admin/migrations/0001_initial.py'
adding 'django/contrib/admin/migrations/0002_logentry_remove_auto_add.py'
adding 'django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py'
adding 'django/contrib/admin/migrations/__init__.py'
adding 'django/contrib/admin/static/admin/css/autocomplete.css'
adding 'django/contrib/admin/static/admin/css/base.css'
adding 'django/contrib/admin/static/admin/css/changelists.css'
adding 'django/contrib/admin/static/admin/css/dark_mode.css'
adding 'django/contrib/admin/static/admin/css/dashboard.css'
adding 'django/contrib/admin/static/admin/css/forms.css'
adding 'django/contrib/admin/static/admin/css/login.css'
adding 'django/contrib/admin/static/admin/css/nav_sidebar.css'
adding 'django/contrib/admin/static/admin/css/responsive.css'
adding 'django/contrib/admin/static/admin/css/responsive_rtl.css'
adding 'django/contrib/admin/static/admin/css/rtl.css'
adding 'django/contrib/admin/static/admin/css/widgets.css'
adding 'django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md'
adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.css'
adding 'django/contrib/admin/static/admin/css/vendor/select2/select2.min.css'
adding 'django/contrib/admin/static/admin/img/LICENSE'
adding 'django/contrib/admin/static/admin/img/README.txt'
adding 'django/contrib/admin/static/admin/img/calendar-icons.svg'
adding 'django/contrib/admin/static/admin/img/icon-addlink.svg'
adding 'django/contrib/admin/static/admin/img/icon-alert.svg'
adding 'django/contrib/admin/static/admin/img/icon-calendar.svg'
adding 'django/contrib/admin/static/admin/img/icon-changelink.svg'
adding 'django/contrib/admin/static/admin/img/icon-clock.svg'
adding 'django/contrib/admin/static/admin/img/icon-deletelink.svg'
adding 'django/contrib/admin/static/admin/img/icon-no.svg'
adding 'django/contrib/admin/static/admin/img/icon-unknown-alt.svg'
adding 'django/contrib/admin/static/admin/img/icon-unknown.svg'
adding 'django/contrib/admin/static/admin/img/icon-viewlink.svg'
adding 'django/contrib/admin/static/admin/img/icon-yes.svg'
adding 'django/contrib/admin/static/admin/img/inline-delete.svg'
adding 'django/contrib/admin/static/admin/img/search.svg'
adding 'django/contrib/admin/static/admin/img/selector-icons.svg'
adding 'django/contrib/admin/static/admin/img/sorting-icons.svg'
adding 'django/contrib/admin/static/admin/img/tooltag-add.svg'
adding 'django/contrib/admin/static/admin/img/tooltag-arrowright.svg'
adding 'django/contrib/admin/static/admin/img/gis/move_vertex_off.svg'
adding 'django/contrib/admin/static/admin/img/gis/move_vertex_on.svg'
adding 'django/contrib/admin/static/admin/js/SelectBox.js'
adding 'django/contrib/admin/static/admin/js/SelectFilter2.js'
adding 'django/contrib/admin/static/admin/js/actions.js'
adding 'django/contrib/admin/static/admin/js/autocomplete.js'
adding 'django/contrib/admin/static/admin/js/calendar.js'
adding 'django/contrib/admin/static/admin/js/cancel.js'
adding 'django/contrib/admin/static/admin/js/change_form.js'
adding 'django/contrib/admin/static/admin/js/collapse.js'
adding 'django/contrib/admin/static/admin/js/core.js'
adding 'django/contrib/admin/static/admin/js/filters.js'
adding 'django/contrib/admin/static/admin/js/inlines.js'
adding 'django/contrib/admin/static/admin/js/jquery.init.js'
adding 'django/contrib/admin/static/admin/js/nav_sidebar.js'
adding 'django/contrib/admin/static/admin/js/popup_response.js'
adding 'django/contrib/admin/static/admin/js/prepopulate.js'
adding 'django/contrib/admin/static/admin/js/prepopulate_init.js'
adding 'django/contrib/admin/static/admin/js/theme.js'
adding 'django/contrib/admin/static/admin/js/urlify.js'
adding 'django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js'
adding 'django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js'
adding 'django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt'
adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.js'
adding 'django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md'
adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js'
adding 'django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js'
adding 'django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt'
adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js'
adding 'django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js'
adding 'django/contrib/admin/templates/admin/404.html'
adding 'django/contrib/admin/templates/admin/500.html'
adding 'django/contrib/admin/templates/admin/actions.html'
adding 'django/contrib/admin/templates/admin/app_index.html'
adding 'django/contrib/admin/templates/admin/app_list.html'
adding 'django/contrib/admin/templates/admin/base.html'
adding 'django/contrib/admin/templates/admin/base_site.html'
adding 'django/contrib/admin/templates/admin/change_form.html'
adding 'django/contrib/admin/templates/admin/change_form_object_tools.html'
adding 'django/contrib/admin/templates/admin/change_list.html'
adding 'django/contrib/admin/templates/admin/change_list_object_tools.html'
adding 'django/contrib/admin/templates/admin/change_list_results.html'
adding 'django/contrib/admin/templates/admin/color_theme_toggle.html'
adding 'django/contrib/admin/templates/admin/date_hierarchy.html'
adding 'django/contrib/admin/templates/admin/delete_confirmation.html'
adding 'django/contrib/admin/templates/admin/delete_selected_confirmation.html'
adding 'django/contrib/admin/templates/admin/filter.html'
adding 'django/contrib/admin/templates/admin/index.html'
adding 'django/contrib/admin/templates/admin/invalid_setup.html'
adding 'django/contrib/admin/templates/admin/login.html'
adding 'django/contrib/admin/templates/admin/nav_sidebar.html'
adding 'django/contrib/admin/templates/admin/object_history.html'
adding 'django/contrib/admin/templates/admin/pagination.html'
adding 'django/contrib/admin/templates/admin/popup_response.html'
adding 'django/contrib/admin/templates/admin/prepopulated_fields_js.html'
adding 'django/contrib/admin/templates/admin/search_form.html'
adding 'django/contrib/admin/templates/admin/submit_line.html'
adding 'django/contrib/admin/templates/admin/auth/user/add_form.html'
adding 'django/contrib/admin/templates/admin/auth/user/change_password.html'
adding 'django/contrib/admin/templates/admin/edit_inline/stacked.html'
adding 'django/contrib/admin/templates/admin/edit_inline/tabular.html'
adding 'django/contrib/admin/templates/admin/includes/fieldset.html'
adding 'django/contrib/admin/templates/admin/includes/object_delete_summary.html'
adding 'django/contrib/admin/templates/admin/widgets/clearable_file_input.html'
adding 'django/contrib/admin/templates/admin/widgets/date.html'
adding 'django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html'
adding 'django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html'
adding 'django/contrib/admin/templates/admin/widgets/radio.html'
adding 'django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html'
adding 'django/contrib/admin/templates/admin/widgets/split_datetime.html'
adding 'django/contrib/admin/templates/admin/widgets/time.html'
adding 'django/contrib/admin/templates/admin/widgets/url.html'
adding 'django/contrib/admin/templates/registration/logged_out.html'
adding 'django/contrib/admin/templates/registration/password_change_done.html'
adding 'django/contrib/admin/templates/registration/password_change_form.html'
adding 'django/contrib/admin/templates/registration/password_reset_complete.html'
adding 'django/contrib/admin/templates/registration/password_reset_confirm.html'
adding 'django/contrib/admin/templates/registration/password_reset_done.html'
adding 'django/contrib/admin/templates/registration/password_reset_email.html'
adding 'django/contrib/admin/templates/registration/password_reset_form.html'
adding 'django/contrib/admin/templatetags/__init__.py'
adding 'django/contrib/admin/templatetags/admin_list.py'
adding 'django/contrib/admin/templatetags/admin_modify.py'
adding 'django/contrib/admin/templatetags/admin_urls.py'
adding 'django/contrib/admin/templatetags/base.py'
adding 'django/contrib/admin/templatetags/log.py'
adding 'django/contrib/admin/views/__init__.py'
adding 'django/contrib/admin/views/autocomplete.py'
adding 'django/contrib/admin/views/decorators.py'
adding 'django/contrib/admin/views/main.py'
adding 'django/contrib/admindocs/__init__.py'
adding 'django/contrib/admindocs/apps.py'
adding 'django/contrib/admindocs/middleware.py'
adding 'django/contrib/admindocs/urls.py'
adding 'django/contrib/admindocs/utils.py'
adding 'django/contrib/admindocs/views.py'
adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/admindocs/templates/admin_doc/bookmarklets.html'
adding 'django/contrib/admindocs/templates/admin_doc/index.html'
adding 'django/contrib/admindocs/templates/admin_doc/missing_docutils.html'
adding 'django/contrib/admindocs/templates/admin_doc/model_detail.html'
adding 'django/contrib/admindocs/templates/admin_doc/model_index.html'
adding 'django/contrib/admindocs/templates/admin_doc/template_detail.html'
adding 'django/contrib/admindocs/templates/admin_doc/template_filter_index.html'
adding 'django/contrib/admindocs/templates/admin_doc/template_tag_index.html'
adding 'django/contrib/admindocs/templates/admin_doc/view_detail.html'
adding 'django/contrib/admindocs/templates/admin_doc/view_index.html'
adding 'django/contrib/auth/__init__.py'
adding 'django/contrib/auth/admin.py'
adding 'django/contrib/auth/apps.py'
adding 'django/contrib/auth/backends.py'
adding 'django/contrib/auth/base_user.py'
adding 'django/contrib/auth/checks.py'
adding 'django/contrib/auth/common-passwords.txt.gz'
adding 'django/contrib/auth/context_processors.py'
adding 'django/contrib/auth/decorators.py'
adding 'django/contrib/auth/forms.py'
adding 'django/contrib/auth/hashers.py'
adding 'django/contrib/auth/middleware.py'
adding 'django/contrib/auth/mixins.py'
adding 'django/contrib/auth/models.py'
adding 'django/contrib/auth/password_validation.py'
adding 'django/contrib/auth/signals.py'
adding 'django/contrib/auth/tokens.py'
adding 'django/contrib/auth/urls.py'
adding 'django/contrib/auth/validators.py'
adding 'django/contrib/auth/views.py'
adding 'django/contrib/auth/handlers/__init__.py'
adding 'django/contrib/auth/handlers/modwsgi.py'
adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/auth/management/__init__.py'
adding 'django/contrib/auth/management/commands/__init__.py'
adding 'django/contrib/auth/management/commands/changepassword.py'
adding 'django/contrib/auth/management/commands/createsuperuser.py'
adding 'django/contrib/auth/migrations/0001_initial.py'
adding 'django/contrib/auth/migrations/0002_alter_permission_name_max_length.py'
adding 'django/contrib/auth/migrations/0003_alter_user_email_max_length.py'
adding 'django/contrib/auth/migrations/0004_alter_user_username_opts.py'
adding 'django/contrib/auth/migrations/0005_alter_user_last_login_null.py'
adding 'django/contrib/auth/migrations/0006_require_contenttypes_0002.py'
adding 'django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py'
adding 'django/contrib/auth/migrations/0008_alter_user_username_max_length.py'
adding 'django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py'
adding 'django/contrib/auth/migrations/0010_alter_group_name_max_length.py'
adding 'django/contrib/auth/migrations/0011_update_proxy_permissions.py'
adding 'django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py'
adding 'django/contrib/auth/migrations/__init__.py'
adding 'django/contrib/auth/templates/auth/widgets/read_only_password_hash.html'
adding 'django/contrib/auth/templates/registration/password_reset_subject.txt'
adding 'django/contrib/contenttypes/__init__.py'
adding 'django/contrib/contenttypes/admin.py'
adding 'django/contrib/contenttypes/apps.py'
adding 'django/contrib/contenttypes/checks.py'
adding 'django/contrib/contenttypes/fields.py'
adding 'django/contrib/contenttypes/forms.py'
adding 'django/contrib/contenttypes/models.py'
adding 'django/contrib/contenttypes/views.py'
adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/contenttypes/management/__init__.py'
adding 'django/contrib/contenttypes/management/commands/__init__.py'
adding 'django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py'
adding 'django/contrib/contenttypes/migrations/0001_initial.py'
adding 'django/contrib/contenttypes/migrations/0002_remove_content_type_name.py'
adding 'django/contrib/contenttypes/migrations/__init__.py'
adding 'django/contrib/flatpages/__init__.py'
adding 'django/contrib/flatpages/admin.py'
adding 'django/contrib/flatpages/apps.py'
adding 'django/contrib/flatpages/forms.py'
adding 'django/contrib/flatpages/middleware.py'
adding 'django/contrib/flatpages/models.py'
adding 'django/contrib/flatpages/sitemaps.py'
adding 'django/contrib/flatpages/urls.py'
adding 'django/contrib/flatpages/views.py'
adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/flatpages/migrations/0001_initial.py'
adding 'django/contrib/flatpages/migrations/__init__.py'
adding 'django/contrib/flatpages/templatetags/__init__.py'
adding 'django/contrib/flatpages/templatetags/flatpages.py'
adding 'django/contrib/gis/__init__.py'
adding 'django/contrib/gis/apps.py'
adding 'django/contrib/gis/feeds.py'
adding 'django/contrib/gis/geometry.py'
adding 'django/contrib/gis/measure.py'
adding 'django/contrib/gis/ptr.py'
adding 'django/contrib/gis/shortcuts.py'
adding 'django/contrib/gis/views.py'
adding 'django/contrib/gis/admin/__init__.py'
adding 'django/contrib/gis/admin/options.py'
adding 'django/contrib/gis/admin/widgets.py'
adding 'django/contrib/gis/db/__init__.py'
adding 'django/contrib/gis/db/backends/__init__.py'
adding 'django/contrib/gis/db/backends/utils.py'
adding 'django/contrib/gis/db/backends/base/__init__.py'
adding 'django/contrib/gis/db/backends/base/adapter.py'
adding 'django/contrib/gis/db/backends/base/features.py'
adding 'django/contrib/gis/db/backends/base/models.py'
adding 'django/contrib/gis/db/backends/base/operations.py'
adding 'django/contrib/gis/db/backends/mysql/__init__.py'
adding 'django/contrib/gis/db/backends/mysql/base.py'
adding 'django/contrib/gis/db/backends/mysql/features.py'
adding 'django/contrib/gis/db/backends/mysql/introspection.py'
adding 'django/contrib/gis/db/backends/mysql/operations.py'
adding 'django/contrib/gis/db/backends/mysql/schema.py'
adding 'django/contrib/gis/db/backends/oracle/__init__.py'
adding 'django/contrib/gis/db/backends/oracle/adapter.py'
adding 'django/contrib/gis/db/backends/oracle/base.py'
adding 'django/contrib/gis/db/backends/oracle/features.py'
adding 'django/contrib/gis/db/backends/oracle/introspection.py'
adding 'django/contrib/gis/db/backends/oracle/models.py'
adding 'django/contrib/gis/db/backends/oracle/operations.py'
adding 'django/contrib/gis/db/backends/oracle/schema.py'
adding 'django/contrib/gis/db/backends/postgis/__init__.py'
adding 'django/contrib/gis/db/backends/postgis/adapter.py'
adding 'django/contrib/gis/db/backends/postgis/base.py'
adding 'django/contrib/gis/db/backends/postgis/const.py'
adding 'django/contrib/gis/db/backends/postgis/features.py'
adding 'django/contrib/gis/db/backends/postgis/introspection.py'
adding 'django/contrib/gis/db/backends/postgis/models.py'
adding 'django/contrib/gis/db/backends/postgis/operations.py'
adding 'django/contrib/gis/db/backends/postgis/pgraster.py'
adding 'django/contrib/gis/db/backends/postgis/schema.py'
adding 'django/contrib/gis/db/backends/spatialite/__init__.py'
adding 'django/contrib/gis/db/backends/spatialite/adapter.py'
adding 'django/contrib/gis/db/backends/spatialite/base.py'
adding 'django/contrib/gis/db/backends/spatialite/client.py'
adding 'django/contrib/gis/db/backends/spatialite/features.py'
adding 'django/contrib/gis/db/backends/spatialite/introspection.py'
adding 'django/contrib/gis/db/backends/spatialite/models.py'
adding 'django/contrib/gis/db/backends/spatialite/operations.py'
adding 'django/contrib/gis/db/backends/spatialite/schema.py'
adding 'django/contrib/gis/db/models/__init__.py'
adding 'django/contrib/gis/db/models/aggregates.py'
adding 'django/contrib/gis/db/models/fields.py'
adding 'django/contrib/gis/db/models/functions.py'
adding 'django/contrib/gis/db/models/lookups.py'
adding 'django/contrib/gis/db/models/proxy.py'
adding 'django/contrib/gis/db/models/sql/__init__.py'
adding 'django/contrib/gis/db/models/sql/conversion.py'
adding 'django/contrib/gis/forms/__init__.py'
adding 'django/contrib/gis/forms/fields.py'
adding 'django/contrib/gis/forms/widgets.py'
adding 'django/contrib/gis/gdal/LICENSE'
adding 'django/contrib/gis/gdal/__init__.py'
adding 'django/contrib/gis/gdal/base.py'
adding 'django/contrib/gis/gdal/datasource.py'
adding 'django/contrib/gis/gdal/driver.py'
adding 'django/contrib/gis/gdal/envelope.py'
adding 'django/contrib/gis/gdal/error.py'
adding 'django/contrib/gis/gdal/feature.py'
adding 'django/contrib/gis/gdal/field.py'
adding 'django/contrib/gis/gdal/geometries.py'
adding 'django/contrib/gis/gdal/geomtype.py'
adding 'django/contrib/gis/gdal/layer.py'
adding 'django/contrib/gis/gdal/libgdal.py'
adding 'django/contrib/gis/gdal/srs.py'
adding 'django/contrib/gis/gdal/prototypes/__init__.py'
adding 'django/contrib/gis/gdal/prototypes/ds.py'
adding 'django/contrib/gis/gdal/prototypes/errcheck.py'
adding 'django/contrib/gis/gdal/prototypes/generation.py'
adding 'django/contrib/gis/gdal/prototypes/geom.py'
adding 'django/contrib/gis/gdal/prototypes/raster.py'
adding 'django/contrib/gis/gdal/prototypes/srs.py'
adding 'django/contrib/gis/gdal/raster/__init__.py'
adding 'django/contrib/gis/gdal/raster/band.py'
adding 'django/contrib/gis/gdal/raster/base.py'
adding 'django/contrib/gis/gdal/raster/const.py'
adding 'django/contrib/gis/gdal/raster/source.py'
adding 'django/contrib/gis/geoip2/__init__.py'
adding 'django/contrib/gis/geoip2/base.py'
adding 'django/contrib/gis/geoip2/resources.py'
adding 'django/contrib/gis/geos/LICENSE'
adding 'django/contrib/gis/geos/__init__.py'
adding 'django/contrib/gis/geos/base.py'
adding 'django/contrib/gis/geos/collections.py'
adding 'django/contrib/gis/geos/coordseq.py'
adding 'django/contrib/gis/geos/error.py'
adding 'django/contrib/gis/geos/factory.py'
adding 'django/contrib/gis/geos/geometry.py'
adding 'django/contrib/gis/geos/io.py'
adding 'django/contrib/gis/geos/libgeos.py'
adding 'django/contrib/gis/geos/linestring.py'
adding 'django/contrib/gis/geos/mutable_list.py'
adding 'django/contrib/gis/geos/point.py'
adding 'django/contrib/gis/geos/polygon.py'
adding 'django/contrib/gis/geos/prepared.py'
adding 'django/contrib/gis/geos/prototypes/__init__.py'
adding 'django/contrib/gis/geos/prototypes/coordseq.py'
adding 'django/contrib/gis/geos/prototypes/errcheck.py'
adding 'django/contrib/gis/geos/prototypes/geom.py'
adding 'django/contrib/gis/geos/prototypes/io.py'
adding 'django/contrib/gis/geos/prototypes/misc.py'
adding 'django/contrib/gis/geos/prototypes/predicates.py'
adding 'django/contrib/gis/geos/prototypes/prepared.py'
adding 'django/contrib/gis/geos/prototypes/threadsafe.py'
adding 'django/contrib/gis/geos/prototypes/topology.py'
adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/gis/management/__init__.py'
adding 'django/contrib/gis/management/commands/__init__.py'
adding 'django/contrib/gis/management/commands/inspectdb.py'
adding 'django/contrib/gis/management/commands/ogrinspect.py'
adding 'django/contrib/gis/serializers/__init__.py'
adding 'django/contrib/gis/serializers/geojson.py'
adding 'django/contrib/gis/sitemaps/__init__.py'
adding 'django/contrib/gis/sitemaps/kml.py'
adding 'django/contrib/gis/sitemaps/views.py'
adding 'django/contrib/gis/static/gis/css/ol3.css'
adding 'django/contrib/gis/static/gis/img/draw_line_off.svg'
adding 'django/contrib/gis/static/gis/img/draw_line_on.svg'
adding 'django/contrib/gis/static/gis/img/draw_point_off.svg'
adding 'django/contrib/gis/static/gis/img/draw_point_on.svg'
adding 'django/contrib/gis/static/gis/img/draw_polygon_off.svg'
adding 'django/contrib/gis/static/gis/img/draw_polygon_on.svg'
adding 'django/contrib/gis/static/gis/js/OLMapWidget.js'
adding 'django/contrib/gis/templates/gis/openlayers-osm.html'
adding 'django/contrib/gis/templates/gis/openlayers.html'
adding 'django/contrib/gis/templates/gis/admin/openlayers.html'
adding 'django/contrib/gis/templates/gis/admin/openlayers.js'
adding 'django/contrib/gis/templates/gis/admin/osm.html'
adding 'django/contrib/gis/templates/gis/admin/osm.js'
adding 'django/contrib/gis/templates/gis/kml/base.kml'
adding 'django/contrib/gis/templates/gis/kml/placemarks.kml'
adding 'django/contrib/gis/utils/__init__.py'
adding 'django/contrib/gis/utils/layermapping.py'
adding 'django/contrib/gis/utils/ogrinfo.py'
adding 'django/contrib/gis/utils/ogrinspect.py'
adding 'django/contrib/gis/utils/srs.py'
adding 'django/contrib/humanize/__init__.py'
adding 'django/contrib/humanize/apps.py'
adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/humanize/templatetags/__init__.py'
adding 'django/contrib/humanize/templatetags/humanize.py'
adding 'django/contrib/messages/__init__.py'
adding 'django/contrib/messages/api.py'
adding 'django/contrib/messages/apps.py'
adding 'django/contrib/messages/constants.py'
adding 'django/contrib/messages/context_processors.py'
adding 'django/contrib/messages/middleware.py'
adding 'django/contrib/messages/utils.py'
adding 'django/contrib/messages/views.py'
adding 'django/contrib/messages/storage/__init__.py'
adding 'django/contrib/messages/storage/base.py'
adding 'django/contrib/messages/storage/cookie.py'
adding 'django/contrib/messages/storage/fallback.py'
adding 'django/contrib/messages/storage/session.py'
adding 'django/contrib/postgres/__init__.py'
adding 'django/contrib/postgres/apps.py'
adding 'django/contrib/postgres/constraints.py'
adding 'django/contrib/postgres/expressions.py'
adding 'django/contrib/postgres/functions.py'
adding 'django/contrib/postgres/indexes.py'
adding 'django/contrib/postgres/lookups.py'
adding 'django/contrib/postgres/operations.py'
adding 'django/contrib/postgres/search.py'
adding 'django/contrib/postgres/serializers.py'
adding 'django/contrib/postgres/signals.py'
adding 'django/contrib/postgres/utils.py'
adding 'django/contrib/postgres/validators.py'
adding 'django/contrib/postgres/aggregates/__init__.py'
adding 'django/contrib/postgres/aggregates/general.py'
adding 'django/contrib/postgres/aggregates/mixins.py'
adding 'django/contrib/postgres/aggregates/statistics.py'
adding 'django/contrib/postgres/fields/__init__.py'
adding 'django/contrib/postgres/fields/array.py'
adding 'django/contrib/postgres/fields/citext.py'
adding 'django/contrib/postgres/fields/hstore.py'
adding 'django/contrib/postgres/fields/jsonb.py'
adding 'django/contrib/postgres/fields/ranges.py'
adding 'django/contrib/postgres/fields/utils.py'
adding 'django/contrib/postgres/forms/__init__.py'
adding 'django/contrib/postgres/forms/array.py'
adding 'django/contrib/postgres/forms/hstore.py'
adding 'django/contrib/postgres/forms/ranges.py'
adding 'django/contrib/postgres/jinja2/postgres/widgets/split_array.html'
adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/postgres/templates/postgres/widgets/split_array.html'
adding 'django/contrib/redirects/__init__.py'
adding 'django/contrib/redirects/admin.py'
adding 'django/contrib/redirects/apps.py'
adding 'django/contrib/redirects/middleware.py'
adding 'django/contrib/redirects/models.py'
adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/redirects/migrations/0001_initial.py'
adding 'django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py'
adding 'django/contrib/redirects/migrations/__init__.py'
adding 'django/contrib/sessions/__init__.py'
adding 'django/contrib/sessions/apps.py'
adding 'django/contrib/sessions/base_session.py'
adding 'django/contrib/sessions/exceptions.py'
adding 'django/contrib/sessions/middleware.py'
adding 'django/contrib/sessions/models.py'
adding 'django/contrib/sessions/serializers.py'
adding 'django/contrib/sessions/backends/__init__.py'
adding 'django/contrib/sessions/backends/base.py'
adding 'django/contrib/sessions/backends/cache.py'
adding 'django/contrib/sessions/backends/cached_db.py'
adding 'django/contrib/sessions/backends/db.py'
adding 'django/contrib/sessions/backends/file.py'
adding 'django/contrib/sessions/backends/signed_cookies.py'
adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/sessions/management/__init__.py'
adding 'django/contrib/sessions/management/commands/__init__.py'
adding 'django/contrib/sessions/management/commands/clearsessions.py'
adding 'django/contrib/sessions/migrations/0001_initial.py'
adding 'django/contrib/sessions/migrations/__init__.py'
adding 'django/contrib/sitemaps/__init__.py'
adding 'django/contrib/sitemaps/apps.py'
adding 'django/contrib/sitemaps/views.py'
adding 'django/contrib/sitemaps/management/__init__.py'
adding 'django/contrib/sitemaps/management/commands/__init__.py'
adding 'django/contrib/sitemaps/management/commands/ping_google.py'
adding 'django/contrib/sitemaps/templates/sitemap.xml'
adding 'django/contrib/sitemaps/templates/sitemap_index.xml'
adding 'django/contrib/sites/__init__.py'
adding 'django/contrib/sites/admin.py'
adding 'django/contrib/sites/apps.py'
adding 'django/contrib/sites/checks.py'
adding 'django/contrib/sites/management.py'
adding 'django/contrib/sites/managers.py'
adding 'django/contrib/sites/middleware.py'
adding 'django/contrib/sites/models.py'
adding 'django/contrib/sites/requests.py'
adding 'django/contrib/sites/shortcuts.py'
adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/af/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ar/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ast/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/az/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/be/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/bg/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/bn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/br/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/bs/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ca/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ckb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/cs/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/cy/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/da/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/de/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/dsb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/el/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/en/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/eo/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/et/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/eu/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fa/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fi/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/fy/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ga/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/gd/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/gl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/he/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hi/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hsb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hu/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/hy/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ia/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/id/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/io/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/is/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/it/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ja/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ka/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/kab/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/kk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/km/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/kn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ko/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ky/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/lb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/lt/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/lv/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/mk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ml/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/mn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/mr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ms/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/my/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/nb/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ne/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/nl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/nn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/os/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pa/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pt/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ro/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ru/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sl/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sq/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sv/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/sw/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ta/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/te/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tg/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/th/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tr/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/tt/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/udm/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/uk/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/ur/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/uz/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/vi/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo'
adding 'django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po'
adding 'django/contrib/sites/migrations/0001_initial.py'
adding 'django/contrib/sites/migrations/0002_alter_domain_unique.py'
adding 'django/contrib/sites/migrations/__init__.py'
adding 'django/contrib/staticfiles/__init__.py'
adding 'django/contrib/staticfiles/apps.py'
adding 'django/contrib/staticfiles/checks.py'
adding 'django/contrib/staticfiles/finders.py'
adding 'django/contrib/staticfiles/handlers.py'
adding 'django/contrib/staticfiles/storage.py'
adding 'django/contrib/staticfiles/testing.py'
adding 'django/contrib/staticfiles/urls.py'
adding 'django/contrib/staticfiles/utils.py'
adding 'django/contrib/staticfiles/views.py'
adding 'django/contrib/staticfiles/management/__init__.py'
adding 'django/contrib/staticfiles/management/commands/__init__.py'
adding 'django/contrib/staticfiles/management/commands/collectstatic.py'
adding 'django/contrib/staticfiles/management/commands/findstatic.py'
adding 'django/contrib/staticfiles/management/commands/runserver.py'
adding 'django/contrib/syndication/__init__.py'
adding 'django/contrib/syndication/apps.py'
adding 'django/contrib/syndication/views.py'
adding 'django/core/__init__.py'
adding 'django/core/asgi.py'
adding 'django/core/exceptions.py'
adding 'django/core/paginator.py'
adding 'django/core/signals.py'
adding 'django/core/signing.py'
adding 'django/core/validators.py'
adding 'django/core/wsgi.py'
adding 'django/core/cache/__init__.py'
adding 'django/core/cache/utils.py'
adding 'django/core/cache/backends/__init__.py'
adding 'django/core/cache/backends/base.py'
adding 'django/core/cache/backends/db.py'
adding 'django/core/cache/backends/dummy.py'
adding 'django/core/cache/backends/filebased.py'
adding 'django/core/cache/backends/locmem.py'
adding 'django/core/cache/backends/memcached.py'
adding 'django/core/cache/backends/redis.py'
adding 'django/core/checks/__init__.py'
adding 'django/core/checks/async_checks.py'
adding 'django/core/checks/caches.py'
adding 'django/core/checks/database.py'
adding 'django/core/checks/files.py'
adding 'django/core/checks/messages.py'
adding 'django/core/checks/model_checks.py'
adding 'django/core/checks/registry.py'
adding 'django/core/checks/templates.py'
adding 'django/core/checks/translation.py'
adding 'django/core/checks/urls.py'
adding 'django/core/checks/compatibility/__init__.py'
adding 'django/core/checks/compatibility/django_4_0.py'
adding 'django/core/checks/security/__init__.py'
adding 'django/core/checks/security/base.py'
adding 'django/core/checks/security/csrf.py'
adding 'django/core/checks/security/sessions.py'
adding 'django/core/files/__init__.py'
adding 'django/core/files/base.py'
adding 'django/core/files/images.py'
adding 'django/core/files/locks.py'
adding 'django/core/files/move.py'
adding 'django/core/files/temp.py'
adding 'django/core/files/uploadedfile.py'
adding 'django/core/files/uploadhandler.py'
adding 'django/core/files/utils.py'
adding 'django/core/files/storage/__init__.py'
adding 'django/core/files/storage/base.py'
adding 'django/core/files/storage/filesystem.py'
adding 'django/core/files/storage/handler.py'
adding 'django/core/files/storage/memory.py'
adding 'django/core/files/storage/mixins.py'
adding 'django/core/handlers/__init__.py'
adding 'django/core/handlers/asgi.py'
adding 'django/core/handlers/base.py'
adding 'django/core/handlers/exception.py'
adding 'django/core/handlers/wsgi.py'
adding 'django/core/mail/__init__.py'
adding 'django/core/mail/message.py'
adding 'django/core/mail/utils.py'
adding 'django/core/mail/backends/__init__.py'
adding 'django/core/mail/backends/base.py'
adding 'django/core/mail/backends/console.py'
adding 'django/core/mail/backends/dummy.py'
adding 'django/core/mail/backends/filebased.py'
adding 'django/core/mail/backends/locmem.py'
adding 'django/core/mail/backends/smtp.py'
adding 'django/core/management/__init__.py'
adding 'django/core/management/base.py'
adding 'django/core/management/color.py'
adding 'django/core/management/sql.py'
adding 'django/core/management/templates.py'
adding 'django/core/management/utils.py'
adding 'django/core/management/commands/__init__.py'
adding 'django/core/management/commands/check.py'
adding 'django/core/management/commands/compilemessages.py'
adding 'django/core/management/commands/createcachetable.py'
adding 'django/core/management/commands/dbshell.py'
adding 'django/core/management/commands/diffsettings.py'
adding 'django/core/management/commands/dumpdata.py'
adding 'django/core/management/commands/flush.py'
adding 'django/core/management/commands/inspectdb.py'
adding 'django/core/management/commands/loaddata.py'
adding 'django/core/management/commands/makemessages.py'
adding 'django/core/management/commands/makemigrations.py'
adding 'django/core/management/commands/migrate.py'
adding 'django/core/management/commands/optimizemigration.py'
adding 'django/core/management/commands/runserver.py'
adding 'django/core/management/commands/sendtestemail.py'
adding 'django/core/management/commands/shell.py'
adding 'django/core/management/commands/showmigrations.py'
adding 'django/core/management/commands/sqlflush.py'
adding 'django/core/management/commands/sqlmigrate.py'
adding 'django/core/management/commands/sqlsequencereset.py'
adding 'django/core/management/commands/squashmigrations.py'
adding 'django/core/management/commands/startapp.py'
adding 'django/core/management/commands/startproject.py'
adding 'django/core/management/commands/test.py'
adding 'django/core/management/commands/testserver.py'
adding 'django/core/serializers/__init__.py'
adding 'django/core/serializers/base.py'
adding 'django/core/serializers/json.py'
adding 'django/core/serializers/jsonl.py'
adding 'django/core/serializers/python.py'
adding 'django/core/serializers/pyyaml.py'
adding 'django/core/serializers/xml_serializer.py'
adding 'django/core/servers/__init__.py'
adding 'django/core/servers/basehttp.py'
adding 'django/db/__init__.py'
adding 'django/db/transaction.py'
adding 'django/db/utils.py'
adding 'django/db/backends/__init__.py'
adding 'django/db/backends/ddl_references.py'
adding 'django/db/backends/signals.py'
adding 'django/db/backends/utils.py'
adding 'django/db/backends/base/__init__.py'
adding 'django/db/backends/base/base.py'
adding 'django/db/backends/base/client.py'
adding 'django/db/backends/base/creation.py'
adding 'django/db/backends/base/features.py'
adding 'django/db/backends/base/introspection.py'
adding 'django/db/backends/base/operations.py'
adding 'django/db/backends/base/schema.py'
adding 'django/db/backends/base/validation.py'
adding 'django/db/backends/dummy/__init__.py'
adding 'django/db/backends/dummy/base.py'
adding 'django/db/backends/dummy/features.py'
adding 'django/db/backends/mysql/__init__.py'
adding 'django/db/backends/mysql/base.py'
adding 'django/db/backends/mysql/client.py'
adding 'django/db/backends/mysql/compiler.py'
adding 'django/db/backends/mysql/creation.py'
adding 'django/db/backends/mysql/features.py'
adding 'django/db/backends/mysql/introspection.py'
adding 'django/db/backends/mysql/operations.py'
adding 'django/db/backends/mysql/schema.py'
adding 'django/db/backends/mysql/validation.py'
adding 'django/db/backends/oracle/__init__.py'
adding 'django/db/backends/oracle/base.py'
adding 'django/db/backends/oracle/client.py'
adding 'django/db/backends/oracle/creation.py'
adding 'django/db/backends/oracle/features.py'
adding 'django/db/backends/oracle/functions.py'
adding 'django/db/backends/oracle/introspection.py'
adding 'django/db/backends/oracle/operations.py'
adding 'django/db/backends/oracle/schema.py'
adding 'django/db/backends/oracle/utils.py'
adding 'django/db/backends/oracle/validation.py'
adding 'django/db/backends/postgresql/__init__.py'
adding 'django/db/backends/postgresql/base.py'
adding 'django/db/backends/postgresql/client.py'
adding 'django/db/backends/postgresql/creation.py'
adding 'django/db/backends/postgresql/features.py'
adding 'django/db/backends/postgresql/introspection.py'
adding 'django/db/backends/postgresql/operations.py'
adding 'django/db/backends/postgresql/psycopg_any.py'
adding 'django/db/backends/postgresql/schema.py'
adding 'django/db/backends/sqlite3/__init__.py'
adding 'django/db/backends/sqlite3/_functions.py'
adding 'django/db/backends/sqlite3/base.py'
adding 'django/db/backends/sqlite3/client.py'
adding 'django/db/backends/sqlite3/creation.py'
adding 'django/db/backends/sqlite3/features.py'
adding 'django/db/backends/sqlite3/introspection.py'
adding 'django/db/backends/sqlite3/operations.py'
adding 'django/db/backends/sqlite3/schema.py'
adding 'django/db/migrations/__init__.py'
adding 'django/db/migrations/autodetector.py'
adding 'django/db/migrations/exceptions.py'
adding 'django/db/migrations/executor.py'
adding 'django/db/migrations/graph.py'
adding 'django/db/migrations/loader.py'
adding 'django/db/migrations/migration.py'
adding 'django/db/migrations/optimizer.py'
adding 'django/db/migrations/questioner.py'
adding 'django/db/migrations/recorder.py'
adding 'django/db/migrations/serializer.py'
adding 'django/db/migrations/state.py'
adding 'django/db/migrations/utils.py'
adding 'django/db/migrations/writer.py'
adding 'django/db/migrations/operations/__init__.py'
adding 'django/db/migrations/operations/base.py'
adding 'django/db/migrations/operations/fields.py'
adding 'django/db/migrations/operations/models.py'
adding 'django/db/migrations/operations/special.py'
adding 'django/db/models/__init__.py'
adding 'django/db/models/aggregates.py'
adding 'django/db/models/base.py'
adding 'django/db/models/constants.py'
adding 'django/db/models/constraints.py'
adding 'django/db/models/deletion.py'
adding 'django/db/models/enums.py'
adding 'django/db/models/expressions.py'
adding 'django/db/models/indexes.py'
adding 'django/db/models/lookups.py'
adding 'django/db/models/manager.py'
adding 'django/db/models/options.py'
adding 'django/db/models/query.py'
adding 'django/db/models/query_utils.py'
adding 'django/db/models/signals.py'
adding 'django/db/models/utils.py'
adding 'django/db/models/fields/__init__.py'
adding 'django/db/models/fields/files.py'
adding 'django/db/models/fields/json.py'
adding 'django/db/models/fields/mixins.py'
adding 'django/db/models/fields/proxy.py'
adding 'django/db/models/fields/related.py'
adding 'django/db/models/fields/related_descriptors.py'
adding 'django/db/models/fields/related_lookups.py'
adding 'django/db/models/fields/reverse_related.py'
adding 'django/db/models/functions/__init__.py'
adding 'django/db/models/functions/comparison.py'
adding 'django/db/models/functions/datetime.py'
adding 'django/db/models/functions/math.py'
adding 'django/db/models/functions/mixins.py'
adding 'django/db/models/functions/text.py'
adding 'django/db/models/functions/window.py'
adding 'django/db/models/sql/__init__.py'
adding 'django/db/models/sql/compiler.py'
adding 'django/db/models/sql/constants.py'
adding 'django/db/models/sql/datastructures.py'
adding 'django/db/models/sql/query.py'
adding 'django/db/models/sql/subqueries.py'
adding 'django/db/models/sql/where.py'
adding 'django/dispatch/__init__.py'
adding 'django/dispatch/dispatcher.py'
adding 'django/dispatch/license.txt'
adding 'django/forms/__init__.py'
adding 'django/forms/boundfield.py'
adding 'django/forms/fields.py'
adding 'django/forms/forms.py'
adding 'django/forms/formsets.py'
adding 'django/forms/models.py'
adding 'django/forms/renderers.py'
adding 'django/forms/utils.py'
adding 'django/forms/widgets.py'
adding 'django/forms/jinja2/django/forms/attrs.html'
adding 'django/forms/jinja2/django/forms/default.html'
adding 'django/forms/jinja2/django/forms/div.html'
adding 'django/forms/jinja2/django/forms/label.html'
adding 'django/forms/jinja2/django/forms/p.html'
adding 'django/forms/jinja2/django/forms/table.html'
adding 'django/forms/jinja2/django/forms/ul.html'
adding 'django/forms/jinja2/django/forms/errors/dict/default.html'
adding 'django/forms/jinja2/django/forms/errors/dict/text.txt'
adding 'django/forms/jinja2/django/forms/errors/dict/ul.html'
adding 'django/forms/jinja2/django/forms/errors/list/default.html'
adding 'django/forms/jinja2/django/forms/errors/list/text.txt'
adding 'django/forms/jinja2/django/forms/errors/list/ul.html'
adding 'django/forms/jinja2/django/forms/formsets/default.html'
adding 'django/forms/jinja2/django/forms/formsets/div.html'
adding 'django/forms/jinja2/django/forms/formsets/p.html'
adding 'django/forms/jinja2/django/forms/formsets/table.html'
adding 'django/forms/jinja2/django/forms/formsets/ul.html'
adding 'django/forms/jinja2/django/forms/widgets/attrs.html'
adding 'django/forms/jinja2/django/forms/widgets/checkbox.html'
adding 'django/forms/jinja2/django/forms/widgets/checkbox_option.html'
adding 'django/forms/jinja2/django/forms/widgets/checkbox_select.html'
adding 'django/forms/jinja2/django/forms/widgets/clearable_file_input.html'
adding 'django/forms/jinja2/django/forms/widgets/date.html'
adding 'django/forms/jinja2/django/forms/widgets/datetime.html'
adding 'django/forms/jinja2/django/forms/widgets/email.html'
adding 'django/forms/jinja2/django/forms/widgets/file.html'
adding 'django/forms/jinja2/django/forms/widgets/hidden.html'
adding 'django/forms/jinja2/django/forms/widgets/input.html'
adding 'django/forms/jinja2/django/forms/widgets/input_option.html'
adding 'django/forms/jinja2/django/forms/widgets/multiple_hidden.html'
adding 'django/forms/jinja2/django/forms/widgets/multiple_input.html'
adding 'django/forms/jinja2/django/forms/widgets/multiwidget.html'
adding 'django/forms/jinja2/django/forms/widgets/number.html'
adding 'django/forms/jinja2/django/forms/widgets/password.html'
adding 'django/forms/jinja2/django/forms/widgets/radio.html'
adding 'django/forms/jinja2/django/forms/widgets/radio_option.html'
adding 'django/forms/jinja2/django/forms/widgets/select.html'
adding 'django/forms/jinja2/django/forms/widgets/select_date.html'
adding 'django/forms/jinja2/django/forms/widgets/select_option.html'
adding 'django/forms/jinja2/django/forms/widgets/splitdatetime.html'
adding 'django/forms/jinja2/django/forms/widgets/splithiddendatetime.html'
adding 'django/forms/jinja2/django/forms/widgets/text.html'
adding 'django/forms/jinja2/django/forms/widgets/textarea.html'
adding 'django/forms/jinja2/django/forms/widgets/time.html'
adding 'django/forms/jinja2/django/forms/widgets/url.html'
adding 'django/forms/templates/django/forms/attrs.html'
adding 'django/forms/templates/django/forms/default.html'
adding 'django/forms/templates/django/forms/div.html'
adding 'django/forms/templates/django/forms/label.html'
adding 'django/forms/templates/django/forms/p.html'
adding 'django/forms/templates/django/forms/table.html'
adding 'django/forms/templates/django/forms/ul.html'
adding 'django/forms/templates/django/forms/errors/dict/default.html'
adding 'django/forms/templates/django/forms/errors/dict/text.txt'
adding 'django/forms/templates/django/forms/errors/dict/ul.html'
adding 'django/forms/templates/django/forms/errors/list/default.html'
adding 'django/forms/templates/django/forms/errors/list/text.txt'
adding 'django/forms/templates/django/forms/errors/list/ul.html'
adding 'django/forms/templates/django/forms/formsets/default.html'
adding 'django/forms/templates/django/forms/formsets/div.html'
adding 'django/forms/templates/django/forms/formsets/p.html'
adding 'django/forms/templates/django/forms/formsets/table.html'
adding 'django/forms/templates/django/forms/formsets/ul.html'
adding 'django/forms/templates/django/forms/widgets/attrs.html'
adding 'django/forms/templates/django/forms/widgets/checkbox.html'
adding 'django/forms/templates/django/forms/widgets/checkbox_option.html'
adding 'django/forms/templates/django/forms/widgets/checkbox_select.html'
adding 'django/forms/templates/django/forms/widgets/clearable_file_input.html'
adding 'django/forms/templates/django/forms/widgets/date.html'
adding 'django/forms/templates/django/forms/widgets/datetime.html'
adding 'django/forms/templates/django/forms/widgets/email.html'
adding 'django/forms/templates/django/forms/widgets/file.html'
adding 'django/forms/templates/django/forms/widgets/hidden.html'
adding 'django/forms/templates/django/forms/widgets/input.html'
adding 'django/forms/templates/django/forms/widgets/input_option.html'
adding 'django/forms/templates/django/forms/widgets/multiple_hidden.html'
adding 'django/forms/templates/django/forms/widgets/multiple_input.html'
adding 'django/forms/templates/django/forms/widgets/multiwidget.html'
adding 'django/forms/templates/django/forms/widgets/number.html'
adding 'django/forms/templates/django/forms/widgets/password.html'
adding 'django/forms/templates/django/forms/widgets/radio.html'
adding 'django/forms/templates/django/forms/widgets/radio_option.html'
adding 'django/forms/templates/django/forms/widgets/select.html'
adding 'django/forms/templates/django/forms/widgets/select_date.html'
adding 'django/forms/templates/django/forms/widgets/select_option.html'
adding 'django/forms/templates/django/forms/widgets/splitdatetime.html'
adding 'django/forms/templates/django/forms/widgets/splithiddendatetime.html'
adding 'django/forms/templates/django/forms/widgets/text.html'
adding 'django/forms/templates/django/forms/widgets/textarea.html'
adding 'django/forms/templates/django/forms/widgets/time.html'
adding 'django/forms/templates/django/forms/widgets/url.html'
adding 'django/http/__init__.py'
adding 'django/http/cookie.py'
adding 'django/http/multipartparser.py'
adding 'django/http/request.py'
adding 'django/http/response.py'
adding 'django/middleware/__init__.py'
adding 'django/middleware/cache.py'
adding 'django/middleware/clickjacking.py'
adding 'django/middleware/common.py'
adding 'django/middleware/csrf.py'
adding 'django/middleware/gzip.py'
adding 'django/middleware/http.py'
adding 'django/middleware/locale.py'
adding 'django/middleware/security.py'
adding 'django/template/__init__.py'
adding 'django/template/autoreload.py'
adding 'django/template/base.py'
adding 'django/template/context.py'
adding 'django/template/context_processors.py'
adding 'django/template/defaultfilters.py'
adding 'django/template/defaulttags.py'
adding 'django/template/engine.py'
adding 'django/template/exceptions.py'
adding 'django/template/library.py'
adding 'django/template/loader.py'
adding 'django/template/loader_tags.py'
adding 'django/template/response.py'
adding 'django/template/smartif.py'
adding 'django/template/utils.py'
adding 'django/template/backends/__init__.py'
adding 'django/template/backends/base.py'
adding 'django/template/backends/django.py'
adding 'django/template/backends/dummy.py'
adding 'django/template/backends/jinja2.py'
adding 'django/template/backends/utils.py'
adding 'django/template/loaders/__init__.py'
adding 'django/template/loaders/app_directories.py'
adding 'django/template/loaders/base.py'
adding 'django/template/loaders/cached.py'
adding 'django/template/loaders/filesystem.py'
adding 'django/template/loaders/locmem.py'
adding 'django/templatetags/__init__.py'
adding 'django/templatetags/cache.py'
adding 'django/templatetags/i18n.py'
adding 'django/templatetags/l10n.py'
adding 'django/templatetags/static.py'
adding 'django/templatetags/tz.py'
adding 'django/test/__init__.py'
adding 'django/test/client.py'
adding 'django/test/html.py'
adding 'django/test/runner.py'
adding 'django/test/selenium.py'
adding 'django/test/signals.py'
adding 'django/test/testcases.py'
adding 'django/test/utils.py'
adding 'django/urls/__init__.py'
adding 'django/urls/base.py'
adding 'django/urls/conf.py'
adding 'django/urls/converters.py'
adding 'django/urls/exceptions.py'
adding 'django/urls/resolvers.py'
adding 'django/urls/utils.py'
adding 'django/utils/__init__.py'
adding 'django/utils/_os.py'
adding 'django/utils/archive.py'
adding 'django/utils/asyncio.py'
adding 'django/utils/autoreload.py'
adding 'django/utils/baseconv.py'
adding 'django/utils/cache.py'
adding 'django/utils/connection.py'
adding 'django/utils/crypto.py'
adding 'django/utils/datastructures.py'
adding 'django/utils/dateformat.py'
adding 'django/utils/dateparse.py'
adding 'django/utils/dates.py'
adding 'django/utils/datetime_safe.py'
adding 'django/utils/deconstruct.py'
adding 'django/utils/decorators.py'
adding 'django/utils/deprecation.py'
adding 'django/utils/duration.py'
adding 'django/utils/encoding.py'
adding 'django/utils/feedgenerator.py'
adding 'django/utils/formats.py'
adding 'django/utils/functional.py'
adding 'django/utils/hashable.py'
adding 'django/utils/html.py'
adding 'django/utils/http.py'
adding 'django/utils/inspect.py'
adding 'django/utils/ipv6.py'
adding 'django/utils/itercompat.py'
adding 'django/utils/jslex.py'
adding 'django/utils/log.py'
adding 'django/utils/lorem_ipsum.py'
adding 'django/utils/module_loading.py'
adding 'django/utils/numberformat.py'
adding 'django/utils/regex_helper.py'
adding 'django/utils/safestring.py'
adding 'django/utils/termcolors.py'
adding 'django/utils/text.py'
adding 'django/utils/timesince.py'
adding 'django/utils/timezone.py'
adding 'django/utils/topological_sort.py'
adding 'django/utils/tree.py'
adding 'django/utils/version.py'
adding 'django/utils/xmlutils.py'
adding 'django/utils/translation/__init__.py'
adding 'django/utils/translation/reloader.py'
adding 'django/utils/translation/template.py'
adding 'django/utils/translation/trans_null.py'
adding 'django/utils/translation/trans_real.py'
adding 'django/views/__init__.py'
adding 'django/views/csrf.py'
adding 'django/views/debug.py'
adding 'django/views/defaults.py'
adding 'django/views/i18n.py'
adding 'django/views/static.py'
adding 'django/views/decorators/__init__.py'
adding 'django/views/decorators/cache.py'
adding 'django/views/decorators/clickjacking.py'
adding 'django/views/decorators/common.py'
adding 'django/views/decorators/csrf.py'
adding 'django/views/decorators/debug.py'
adding 'django/views/decorators/gzip.py'
adding 'django/views/decorators/http.py'
adding 'django/views/decorators/vary.py'
adding 'django/views/generic/__init__.py'
adding 'django/views/generic/base.py'
adding 'django/views/generic/dates.py'
adding 'django/views/generic/detail.py'
adding 'django/views/generic/edit.py'
adding 'django/views/generic/list.py'
adding 'django/views/templates/default_urlconf.html'
adding 'django/views/templates/technical_404.html'
adding 'django/views/templates/technical_500.html'
adding 'django/views/templates/technical_500.txt'
adding 'Django-4.2.3.dist-info/AUTHORS'
adding 'Django-4.2.3.dist-info/LICENSE'
adding 'Django-4.2.3.dist-info/LICENSE.python'
adding 'Django-4.2.3.dist-info/METADATA'
adding 'Django-4.2.3.dist-info/WHEEL'
adding 'Django-4.2.3.dist-info/entry_points.txt'
adding 'Django-4.2.3.dist-info/top_level.txt'
adding 'Django-4.2.3.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
Building wheel for Django (pyproject.toml): finished with status 'done'
Created wheel for Django: filename=Django-4.2.3-py3-none-any.whl size=7989942 sha256=415ebacb8b2fb7ba51f8068b8cb7c89c39a39b5faef3a984215fb023181aeb57
Stored in directory: /builddir/.cache/pip/wheels/f0/72/84/f6b381a260551edce5381c6e394f514aadd51f170176405f40
Successfully built Django
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.kdCudm
+ umask 022
+ cd /builddir/build/BUILD
+ '[' /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64 '!=' / ']'
+ rm -rf /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64
++ dirname /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64
+ mkdir -p /builddir/build/BUILDROOT
+ mkdir /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd Django-4.2.3
++ xargs basename --multiple
++ ls /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir/Django-4.2.3-py3-none-any.whl
++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/'
+ specifier=Django==4.2.3
+ TMPDIR=/builddir/build/BUILD/Django-4.2.3/.pyproject-builddir
+ /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64 --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir Django==4.2.3
Using pip 23.2.1 from /usr/lib/python3.12/site-packages/pip (python 3.12)
Looking in links: /builddir/build/BUILD/Django-4.2.3/pyproject-wheeldir
Processing ./pyproject-wheeldir/Django-4.2.3-py3-none-any.whl
Installing collected packages: Django
Creating /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin
changing mode of /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin/django-admin to 755
Successfully installed Django-4.2.3
+ '[' -d /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin ']'
+ '[' -z sP ']'
+ shebang_flags=-kasP
+ /usr/bin/python3 -B /usr/lib/rpm/redhat/pathfix.py -pni /usr/bin/python3 -kasP /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin/django-admin
/builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin/django-admin: updating
+ rm -rfv /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin/__pycache__
+ rm -f /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-ghost-distinfo
+ site_dirs=()
+ '[' -d /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages ']'
+ site_dirs+=("/usr/lib/python3.12/site-packages")
+ '[' /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib64/python3.12/site-packages '!=' /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages ']'
+ '[' -d /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib64/python3.12/site-packages ']'
+ for site_dir in ${site_dirs[@]}
+ for distinfo in /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64$site_dir/*.dist-info
+ echo '%ghost /usr/lib/python3.12/site-packages/Django-4.2.3.dist-info'
+ sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages/Django-4.2.3.dist-info/INSTALLER
+ PYTHONPATH=/usr/lib/rpm/redhat
+ /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64 --record /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages/Django-4.2.3.dist-info/RECORD --output /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-record
+ rm -fv /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages/Django-4.2.3.dist-info/RECORD
removed '/builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages/Django-4.2.3.dist-info/RECORD'
+ rm -fv /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages/Django-4.2.3.dist-info/REQUESTED
removed '/builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12/site-packages/Django-4.2.3.dist-info/REQUESTED'
++ wc -l /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-ghost-distinfo
++ cut -f1 '-d '
+ lines=1
+ '[' 1 -ne 1 ']'
+ RPM_PERCENTAGES_COUNT=2
+ /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-files --output-modules /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-modules --buildroot /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64 --sitelib /usr/lib/python3.12/site-packages --sitearch /usr/lib64/python3.12/site-packages --python-version 3.12 --pyproject-record /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-record --prefix /usr django
+ cd docs
+ mkdir djangohtml
+ mkdir -p _build/doctrees _build/html
+ make html
sphinx-build -b djangohtml -n -d _build/doctrees -D language=en . _build/html
Running Sphinx v7.0.1
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from https://www.sphinx-doc.org/en/master/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable due to <class 'requests.exceptions.ConnectionError'>: HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /3/objects.inv (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f3c6740cf20>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
loading intersphinx inventory from https://www.psycopg.org/psycopg3/docs/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://www.sphinx-doc.org/en/master/objects.inv' not fetchable due to <class 'requests.exceptions.ConnectionError'>: HTTPSConnectionPool(host='www.sphinx-doc.org', port=443): Max retries exceeded with url: /en/master/objects.inv (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f3c6740d580>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://www.psycopg.org/psycopg3/docs/objects.inv' not fetchable due to <class 'requests.exceptions.ConnectionError'>: HTTPSConnectionPool(host='www.psycopg.org', port=443): Max retries exceeded with url: /psycopg3/docs/objects.inv (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f3c6740d9d0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
building [mo]: targets for 0 po files that are out of date
writing output...
building [djangohtml]: targets for 564 source files that are out of date
updating environment: [new config] 564 added, 0 changed, 0 removed
reading sources... [ 0%] contents
reading sources... [ 0%] faq/admin
reading sources... [ 0%] faq/contributing
reading sources... [ 0%] faq/general
reading sources... [ 0%] faq/help
reading sources... [ 1%] faq/index
reading sources... [ 1%] faq/install
reading sources... [ 1%] faq/models
reading sources... [ 1%] faq/troubleshooting
reading sources... [ 1%] faq/usage
reading sources... [ 1%] glossary
reading sources... [ 2%] howto/auth-remote-user
reading sources... [ 2%] howto/csrf
reading sources... [ 2%] howto/custom-file-storage
reading sources... [ 2%] howto/custom-lookups
reading sources... [ 2%] howto/custom-management-commands
reading sources... [ 3%] howto/custom-model-fields
reading sources... [ 3%] howto/custom-template-backend
reading sources... [ 3%] howto/custom-template-tags
reading sources... [ 3%] howto/deployment/asgi/daphne
reading sources... [ 3%] howto/deployment/asgi/hypercorn
reading sources... [ 3%] howto/deployment/asgi/index
reading sources... [ 4%] howto/deployment/asgi/uvicorn
reading sources... [ 4%] howto/deployment/checklist
reading sources... [ 4%] howto/deployment/index
reading sources... [ 4%] howto/deployment/wsgi/apache-auth
reading sources... [ 4%] howto/deployment/wsgi/gunicorn
reading sources... [ 4%] howto/deployment/wsgi/index
reading sources... [ 5%] howto/deployment/wsgi/modwsgi
reading sources... [ 5%] howto/deployment/wsgi/uwsgi
reading sources... [ 5%] howto/error-reporting
reading sources... [ 5%] howto/index
reading sources... [ 5%] howto/initial-data
reading sources... [ 6%] howto/legacy-databases
reading sources... [ 6%] howto/logging
reading sources... [ 6%] howto/outputting-csv
reading sources... [ 6%] howto/outputting-pdf
reading sources... [ 6%] howto/overriding-templates
reading sources... [ 6%] howto/static-files/deployment
reading sources... [ 7%] howto/static-files/index
reading sources... [ 7%] howto/upgrade-version
reading sources... [ 7%] howto/windows
reading sources... [ 7%] howto/writing-migrations
reading sources... [ 7%] index
reading sources... [ 7%] internals/contributing/bugs-and-features
reading sources... [ 8%] internals/contributing/committing-code
reading sources... [ 8%] internals/contributing/index
reading sources... [ 8%] internals/contributing/localizing
reading sources... [ 8%] internals/contributing/new-contributors
reading sources... [ 8%] internals/contributing/triaging-tickets
reading sources... [ 9%] internals/contributing/writing-code/coding-style
reading sources... [ 9%] internals/contributing/writing-code/index
reading sources... [ 9%] internals/contributing/writing-code/javascript
reading sources... [ 9%] internals/contributing/writing-code/submitting-patches
reading sources... [ 9%] internals/contributing/writing-code/unit-tests
reading sources... [ 9%] internals/contributing/writing-code/working-with-git
reading sources... [ 10%] internals/contributing/writing-documentation
reading sources... [ 10%] internals/deprecation
reading sources... [ 10%] internals/git
reading sources... [ 10%] internals/howto-release-django
reading sources... [ 10%] internals/index
reading sources... [ 10%] internals/mailing-lists
reading sources... [ 11%] internals/organization
reading sources... [ 11%] internals/release-process
reading sources... [ 11%] internals/security
reading sources... [ 11%] intro/contributing
reading sources... [ 11%] intro/index
reading sources... [ 12%] intro/install
reading sources... [ 12%] intro/overview
reading sources... [ 12%] intro/reusable-apps
reading sources... [ 12%] intro/tutorial01
reading sources... [ 12%] intro/tutorial02
reading sources... [ 12%] intro/tutorial03
reading sources... [ 13%] intro/tutorial04
reading sources... [ 13%] intro/tutorial05
reading sources... [ 13%] intro/tutorial06
reading sources... [ 13%] intro/tutorial07
reading sources... [ 13%] intro/tutorial08
reading sources... [ 14%] intro/whatsnext
reading sources... [ 14%] misc/api-stability
reading sources... [ 14%] misc/design-philosophies
reading sources... [ 14%] misc/distributions
reading sources... [ 14%] misc/index
reading sources... [ 14%] ref/applications
reading sources... [ 15%] ref/checks
reading sources... [ 15%] ref/class-based-views/base
reading sources... [ 15%] ref/class-based-views/flattened-index
reading sources... [ 15%] ref/class-based-views/generic-date-based
reading sources... [ 15%] ref/class-based-views/generic-display
reading sources... [ 15%] ref/class-based-views/generic-editing
reading sources... [ 16%] ref/class-based-views/index
reading sources... [ 16%] ref/class-based-views/mixins
reading sources... [ 16%] ref/class-based-views/mixins-date-based
reading sources... [ 16%] ref/class-based-views/mixins-editing
reading sources... [ 16%] ref/class-based-views/mixins-multiple-object
reading sources... [ 17%] ref/class-based-views/mixins-simple
reading sources... [ 17%] ref/class-based-views/mixins-single-object
reading sources... [ 17%] ref/clickjacking
reading sources... [ 17%] ref/contrib/admin/actions
reading sources... [ 17%] ref/contrib/admin/admindocs
reading sources... [ 17%] ref/contrib/admin/filters
reading sources... [ 18%] ref/contrib/admin/index
reading sources... [ 18%] ref/contrib/admin/javascript
reading sources... [ 18%] ref/contrib/auth
reading sources... [ 18%] ref/contrib/contenttypes
reading sources... [ 18%] ref/contrib/flatpages
reading sources... [ 18%] ref/contrib/gis/admin
reading sources... [ 19%] ref/contrib/gis/commands
reading sources... [ 19%] ref/contrib/gis/db-api
reading sources... [ 19%] ref/contrib/gis/deployment
reading sources... [ 19%] ref/contrib/gis/feeds
reading sources... [ 19%] ref/contrib/gis/forms-api
reading sources... [ 20%] ref/contrib/gis/functions
reading sources... [ 20%] ref/contrib/gis/gdal
reading sources... [ 20%] ref/contrib/gis/geoip2
reading sources... [ 20%] ref/contrib/gis/geoquerysets
reading sources... [ 20%] ref/contrib/gis/geos
reading sources... [ 20%] ref/contrib/gis/index
reading sources... [ 21%] ref/contrib/gis/install/geolibs
reading sources... [ 21%] ref/contrib/gis/install/index
reading sources... [ 21%] ref/contrib/gis/install/postgis
reading sources... [ 21%] ref/contrib/gis/install/spatialite
reading sources... [ 21%] ref/contrib/gis/layermapping
reading sources... [ 21%] ref/contrib/gis/measure
reading sources... [ 22%] ref/contrib/gis/model-api
reading sources... [ 22%] ref/contrib/gis/ogrinspect
reading sources... [ 22%] ref/contrib/gis/serializers
reading sources... [ 22%] ref/contrib/gis/sitemaps
reading sources... [ 22%] ref/contrib/gis/testing
reading sources... [ 23%] ref/contrib/gis/tutorial
reading sources... [ 23%] ref/contrib/gis/utils
reading sources... [ 23%] ref/contrib/humanize
reading sources... [ 23%] ref/contrib/index
reading sources... [ 23%] ref/contrib/messages
reading sources... [ 23%] ref/contrib/postgres/aggregates
reading sources... [ 24%] ref/contrib/postgres/constraints
reading sources... [ 24%] ref/contrib/postgres/expressions
reading sources... [ 24%] ref/contrib/postgres/fields
reading sources... [ 24%] ref/contrib/postgres/forms
reading sources... [ 24%] ref/contrib/postgres/functions
reading sources... [ 25%] ref/contrib/postgres/index
reading sources... [ 25%] ref/contrib/postgres/indexes
reading sources... [ 25%] ref/contrib/postgres/lookups
reading sources... [ 25%] ref/contrib/postgres/operations
reading sources... [ 25%] ref/contrib/postgres/search
reading sources... [ 25%] ref/contrib/postgres/validators
reading sources... [ 26%] ref/contrib/redirects
reading sources... [ 26%] ref/contrib/sitemaps
reading sources... [ 26%] ref/contrib/sites
reading sources... [ 26%] ref/contrib/staticfiles
reading sources... [ 26%] ref/contrib/syndication
reading sources... [ 26%] ref/csrf
reading sources... [ 27%] ref/databases
reading sources... [ 27%] ref/django-admin
reading sources... [ 27%] ref/exceptions
reading sources... [ 27%] ref/files/file
reading sources... [ 27%] ref/files/index
reading sources... [ 28%] ref/files/storage
reading sources... [ 28%] ref/files/uploads
reading sources... [ 28%] ref/forms/api
reading sources... [ 28%] ref/forms/fields
reading sources... [ 28%] ref/forms/formsets
reading sources... [ 28%] ref/forms/index
reading sources... [ 29%] ref/forms/models
reading sources... [ 29%] ref/forms/renderers
reading sources... [ 29%] ref/forms/validation
reading sources... [ 29%] ref/forms/widgets
reading sources... [ 29%] ref/index
reading sources... [ 29%] ref/logging
reading sources... [ 30%] ref/middleware
reading sources... [ 30%] ref/migration-operations
reading sources... [ 30%] ref/models/class
reading sources... [ 30%] ref/models/conditional-expressions
reading sources... [ 30%] ref/models/constraints
reading sources... [ 31%] ref/models/database-functions
reading sources... [ 31%] ref/models/expressions
reading sources... [ 31%] ref/models/fields
reading sources... [ 31%] ref/models/index
reading sources... [ 31%] ref/models/indexes
reading sources... [ 31%] ref/models/instances
reading sources... [ 32%] ref/models/lookups
reading sources... [ 32%] ref/models/meta
reading sources... [ 32%] ref/models/options
reading sources... [ 32%] ref/models/querysets
reading sources... [ 32%] ref/models/relations
reading sources... [ 32%] ref/paginator
reading sources... [ 33%] ref/request-response
reading sources... [ 33%] ref/schema-editor
reading sources... [ 33%] ref/settings
reading sources... [ 33%] ref/signals
reading sources... [ 33%] ref/template-response
reading sources... [ 34%] ref/templates/api
reading sources... [ 34%] ref/templates/builtins
reading sources... [ 34%] ref/templates/index
reading sources... [ 34%] ref/templates/language
reading sources... [ 34%] ref/unicode
reading sources... [ 34%] ref/urlresolvers
reading sources... [ 35%] ref/urls
reading sources... [ 35%] ref/utils
reading sources... [ 35%] ref/validators
reading sources... [ 35%] ref/views
reading sources... [ 35%] releases/0.95
reading sources... [ 35%] releases/0.96
reading sources... [ 36%] releases/1.0
reading sources... [ 36%] releases/1.0-porting-guide
reading sources... [ 36%] releases/1.0.1
reading sources... [ 36%] releases/1.0.2
reading sources... [ 36%] releases/1.1
reading sources... [ 37%] releases/1.1.2
reading sources... [ 37%] releases/1.1.3
reading sources... [ 37%] releases/1.1.4
reading sources... [ 37%] releases/1.10
reading sources... [ 37%] releases/1.10.1
reading sources... [ 37%] releases/1.10.2
reading sources... [ 38%] releases/1.10.3
reading sources... [ 38%] releases/1.10.4
reading sources... [ 38%] releases/1.10.5
reading sources... [ 38%] releases/1.10.6
reading sources... [ 38%] releases/1.10.7
reading sources... [ 39%] releases/1.10.8
reading sources... [ 39%] releases/1.11
reading sources... [ 39%] releases/1.11.1
reading sources... [ 39%] releases/1.11.10
reading sources... [ 39%] releases/1.11.11
reading sources... [ 39%] releases/1.11.12
reading sources... [ 40%] releases/1.11.13
reading sources... [ 40%] releases/1.11.14
reading sources... [ 40%] releases/1.11.15
reading sources... [ 40%] releases/1.11.16
reading sources... [ 40%] releases/1.11.17
reading sources... [ 40%] releases/1.11.18
reading sources... [ 41%] releases/1.11.19
reading sources... [ 41%] releases/1.11.2
reading sources... [ 41%] releases/1.11.20
reading sources... [ 41%] releases/1.11.21
reading sources... [ 41%] releases/1.11.22
reading sources... [ 42%] releases/1.11.23
reading sources... [ 42%] releases/1.11.24
reading sources... [ 42%] releases/1.11.25
reading sources... [ 42%] releases/1.11.26
reading sources... [ 42%] releases/1.11.27
reading sources... [ 42%] releases/1.11.28
reading sources... [ 43%] releases/1.11.29
reading sources... [ 43%] releases/1.11.3
reading sources... [ 43%] releases/1.11.4
reading sources... [ 43%] releases/1.11.5
reading sources... [ 43%] releases/1.11.6
reading sources... [ 43%] releases/1.11.7
reading sources... [ 44%] releases/1.11.8
reading sources... [ 44%] releases/1.11.9
reading sources... [ 44%] releases/1.2
reading sources... [ 44%] releases/1.2.1
reading sources... [ 44%] releases/1.2.2
reading sources... [ 45%] releases/1.2.3
reading sources... [ 45%] releases/1.2.4
reading sources... [ 45%] releases/1.2.5
reading sources... [ 45%] releases/1.2.6
reading sources... [ 45%] releases/1.2.7
reading sources... [ 45%] releases/1.3
reading sources... [ 46%] releases/1.3.1
reading sources... [ 46%] releases/1.3.2
reading sources... [ 46%] releases/1.3.3
reading sources... [ 46%] releases/1.3.4
reading sources... [ 46%] releases/1.3.5
reading sources... [ 46%] releases/1.3.6
reading sources... [ 47%] releases/1.3.7
reading sources... [ 47%] releases/1.4
reading sources... [ 47%] releases/1.4.1
reading sources... [ 47%] releases/1.4.10
reading sources... [ 47%] releases/1.4.11
reading sources... [ 48%] releases/1.4.12
reading sources... [ 48%] releases/1.4.13
reading sources... [ 48%] releases/1.4.14
reading sources... [ 48%] releases/1.4.15
reading sources... [ 48%] releases/1.4.16
reading sources... [ 48%] releases/1.4.17
reading sources... [ 49%] releases/1.4.18
reading sources... [ 49%] releases/1.4.19
reading sources... [ 49%] releases/1.4.2
reading sources... [ 49%] releases/1.4.20
reading sources... [ 49%] releases/1.4.21
reading sources... [ 50%] releases/1.4.22
reading sources... [ 50%] releases/1.4.3
reading sources... [ 50%] releases/1.4.4
reading sources... [ 50%] releases/1.4.5
reading sources... [ 50%] releases/1.4.6
reading sources... [ 50%] releases/1.4.7
reading sources... [ 51%] releases/1.4.8
reading sources... [ 51%] releases/1.4.9
reading sources... [ 51%] releases/1.5
reading sources... [ 51%] releases/1.5.1
reading sources... [ 51%] releases/1.5.10
reading sources... [ 51%] releases/1.5.11
reading sources... [ 52%] releases/1.5.12
reading sources... [ 52%] releases/1.5.2
reading sources... [ 52%] releases/1.5.3
reading sources... [ 52%] releases/1.5.4
reading sources... [ 52%] releases/1.5.5
reading sources... [ 53%] releases/1.5.6
reading sources... [ 53%] releases/1.5.7
reading sources... [ 53%] releases/1.5.8
reading sources... [ 53%] releases/1.5.9
reading sources... [ 53%] releases/1.6
reading sources... [ 53%] releases/1.6.1
reading sources... [ 54%] releases/1.6.10
reading sources... [ 54%] releases/1.6.11
reading sources... [ 54%] releases/1.6.2
reading sources... [ 54%] releases/1.6.3
reading sources... [ 54%] releases/1.6.4
reading sources... [ 54%] releases/1.6.5
reading sources... [ 55%] releases/1.6.6
reading sources... [ 55%] releases/1.6.7
reading sources... [ 55%] releases/1.6.8
reading sources... [ 55%] releases/1.6.9
reading sources... [ 55%] releases/1.7
reading sources... [ 56%] releases/1.7.1
reading sources... [ 56%] releases/1.7.10
reading sources... [ 56%] releases/1.7.11
reading sources... [ 56%] releases/1.7.2
reading sources... [ 56%] releases/1.7.3
reading sources... [ 56%] releases/1.7.4
reading sources... [ 57%] releases/1.7.5
reading sources... [ 57%] releases/1.7.6
reading sources... [ 57%] releases/1.7.7
reading sources... [ 57%] releases/1.7.8
reading sources... [ 57%] releases/1.7.9
reading sources... [ 57%] releases/1.8
reading sources... [ 58%] releases/1.8.1
reading sources... [ 58%] releases/1.8.10
reading sources... [ 58%] releases/1.8.11
reading sources... [ 58%] releases/1.8.12
reading sources... [ 58%] releases/1.8.13
reading sources... [ 59%] releases/1.8.14
reading sources... [ 59%] releases/1.8.15
reading sources... [ 59%] releases/1.8.16
reading sources... [ 59%] releases/1.8.17
reading sources... [ 59%] releases/1.8.18
reading sources... [ 59%] releases/1.8.19
reading sources... [ 60%] releases/1.8.2
reading sources... [ 60%] releases/1.8.3
reading sources... [ 60%] releases/1.8.4
reading sources... [ 60%] releases/1.8.5
reading sources... [ 60%] releases/1.8.6
reading sources... [ 60%] releases/1.8.7
reading sources... [ 61%] releases/1.8.8
reading sources... [ 61%] releases/1.8.9
reading sources... [ 61%] releases/1.9
reading sources... [ 61%] releases/1.9.1
reading sources... [ 61%] releases/1.9.10
reading sources... [ 62%] releases/1.9.11
reading sources... [ 62%] releases/1.9.12
reading sources... [ 62%] releases/1.9.13
reading sources... [ 62%] releases/1.9.2
reading sources... [ 62%] releases/1.9.3
reading sources... [ 62%] releases/1.9.4
reading sources... [ 63%] releases/1.9.5
reading sources... [ 63%] releases/1.9.6
reading sources... [ 63%] releases/1.9.7
reading sources... [ 63%] releases/1.9.8
reading sources... [ 63%] releases/1.9.9
reading sources... [ 64%] releases/2.0
reading sources... [ 64%] releases/2.0.1
reading sources... [ 64%] releases/2.0.10
reading sources... [ 64%] releases/2.0.11
reading sources... [ 64%] releases/2.0.12
reading sources... [ 64%] releases/2.0.13
reading sources... [ 65%] releases/2.0.2
reading sources... [ 65%] releases/2.0.3
reading sources... [ 65%] releases/2.0.4
reading sources... [ 65%] releases/2.0.5
reading sources... [ 65%] releases/2.0.6
reading sources... [ 65%] releases/2.0.7
reading sources... [ 66%] releases/2.0.8
reading sources... [ 66%] releases/2.0.9
reading sources... [ 66%] releases/2.1
reading sources... [ 66%] releases/2.1.1
reading sources... [ 66%] releases/2.1.10
reading sources... [ 67%] releases/2.1.11
reading sources... [ 67%] releases/2.1.12
reading sources... [ 67%] releases/2.1.13
reading sources... [ 67%] releases/2.1.14
reading sources... [ 67%] releases/2.1.15
reading sources... [ 67%] releases/2.1.2
reading sources... [ 68%] releases/2.1.3
reading sources... [ 68%] releases/2.1.4
reading sources... [ 68%] releases/2.1.5
reading sources... [ 68%] releases/2.1.6
reading sources... [ 68%] releases/2.1.7
reading sources... [ 68%] releases/2.1.8
reading sources... [ 69%] releases/2.1.9
reading sources... [ 69%] releases/2.2
reading sources... [ 69%] releases/2.2.1
reading sources... [ 69%] releases/2.2.10
reading sources... [ 69%] releases/2.2.11
reading sources... [ 70%] releases/2.2.12
reading sources... [ 70%] releases/2.2.13
reading sources... [ 70%] releases/2.2.14
reading sources... [ 70%] releases/2.2.15
reading sources... [ 70%] releases/2.2.16
reading sources... [ 70%] releases/2.2.17
reading sources... [ 71%] releases/2.2.18
reading sources... [ 71%] releases/2.2.19
reading sources... [ 71%] releases/2.2.2
reading sources... [ 71%] releases/2.2.20
reading sources... [ 71%] releases/2.2.21
reading sources... [ 71%] releases/2.2.22
reading sources... [ 72%] releases/2.2.23
reading sources... [ 72%] releases/2.2.24
reading sources... [ 72%] releases/2.2.25
reading sources... [ 72%] releases/2.2.26
reading sources... [ 72%] releases/2.2.27
reading sources... [ 73%] releases/2.2.28
reading sources... [ 73%] releases/2.2.3
reading sources... [ 73%] releases/2.2.4
reading sources... [ 73%] releases/2.2.5
reading sources... [ 73%] releases/2.2.6
reading sources... [ 73%] releases/2.2.7
reading sources... [ 74%] releases/2.2.8
reading sources... [ 74%] releases/2.2.9
reading sources... [ 74%] releases/3.0
reading sources... [ 74%] releases/3.0.1
reading sources... [ 74%] releases/3.0.10
reading sources... [ 75%] releases/3.0.11
reading sources... [ 75%] releases/3.0.12
reading sources... [ 75%] releases/3.0.13
reading sources... [ 75%] releases/3.0.14
reading sources... [ 75%] releases/3.0.2
reading sources... [ 75%] releases/3.0.3
reading sources... [ 76%] releases/3.0.4
reading sources... [ 76%] releases/3.0.5
reading sources... [ 76%] releases/3.0.6
reading sources... [ 76%] releases/3.0.7
reading sources... [ 76%] releases/3.0.8
reading sources... [ 76%] releases/3.0.9
reading sources... [ 77%] releases/3.1
reading sources... [ 77%] releases/3.1.1
reading sources... [ 77%] releases/3.1.10
reading sources... [ 77%] releases/3.1.11
reading sources... [ 77%] releases/3.1.12
reading sources... [ 78%] releases/3.1.13
reading sources... [ 78%] releases/3.1.14
reading sources... [ 78%] releases/3.1.2
reading sources... [ 78%] releases/3.1.3
reading sources... [ 78%] releases/3.1.4
reading sources... [ 78%] releases/3.1.5
reading sources... [ 79%] releases/3.1.6
reading sources... [ 79%] releases/3.1.7
reading sources... [ 79%] releases/3.1.8
reading sources... [ 79%] releases/3.1.9
reading sources... [ 79%] releases/3.2
reading sources... [ 79%] releases/3.2.1
reading sources... [ 80%] releases/3.2.10
reading sources... [ 80%] releases/3.2.11
reading sources... [ 80%] releases/3.2.12
reading sources... [ 80%] releases/3.2.13
reading sources... [ 80%] releases/3.2.14
reading sources... [ 81%] releases/3.2.15
reading sources... [ 81%] releases/3.2.16
reading sources... [ 81%] releases/3.2.17
reading sources... [ 81%] releases/3.2.18
reading sources... [ 81%] releases/3.2.19
reading sources... [ 81%] releases/3.2.2
reading sources... [ 82%] releases/3.2.20
reading sources... [ 82%] releases/3.2.3
reading sources... [ 82%] releases/3.2.4
reading sources... [ 82%] releases/3.2.5
reading sources... [ 82%] releases/3.2.6
reading sources... [ 82%] releases/3.2.7
reading sources... [ 83%] releases/3.2.8
reading sources... [ 83%] releases/3.2.9
reading sources... [ 83%] releases/4.0
reading sources... [ 83%] releases/4.0.1
reading sources... [ 83%] releases/4.0.10
reading sources... [ 84%] releases/4.0.2
reading sources... [ 84%] releases/4.0.3
reading sources... [ 84%] releases/4.0.4
reading sources... [ 84%] releases/4.0.5
reading sources... [ 84%] releases/4.0.6
reading sources... [ 84%] releases/4.0.7
reading sources... [ 85%] releases/4.0.8
reading sources... [ 85%] releases/4.0.9
reading sources... [ 85%] releases/4.1
reading sources... [ 85%] releases/4.1.1
reading sources... [ 85%] releases/4.1.10
reading sources... [ 85%] releases/4.1.2
reading sources... [ 86%] releases/4.1.3
reading sources... [ 86%] releases/4.1.4
reading sources... [ 86%] releases/4.1.5
reading sources... [ 86%] releases/4.1.6
reading sources... [ 86%] releases/4.1.7
reading sources... [ 87%] releases/4.1.8
reading sources... [ 87%] releases/4.1.9
reading sources... [ 87%] releases/4.2
reading sources... [ 87%] releases/4.2.1
reading sources... [ 87%] releases/4.2.2
reading sources... [ 87%] releases/4.2.3
reading sources... [ 88%] releases/index
reading sources... [ 88%] releases/security
reading sources... [ 88%] topics/async
reading sources... [ 88%] topics/auth/customizing
reading sources... [ 88%] topics/auth/default
reading sources... [ 89%] topics/auth/index
reading sources... [ 89%] topics/auth/passwords
reading sources... [ 89%] topics/cache
reading sources... [ 89%] topics/checks
reading sources... [ 89%] topics/class-based-views/generic-display
reading sources... [ 89%] topics/class-based-views/generic-editing
reading sources... [ 90%] topics/class-based-views/index
reading sources... [ 90%] topics/class-based-views/intro
reading sources... [ 90%] topics/class-based-views/mixins
reading sources... [ 90%] topics/conditional-view-processing
reading sources... [ 90%] topics/db/aggregation
reading sources... [ 90%] topics/db/examples/index
reading sources... [ 91%] topics/db/examples/many_to_many
reading sources... [ 91%] topics/db/examples/many_to_one
reading sources... [ 91%] topics/db/examples/one_to_one
reading sources... [ 91%] topics/db/fixtures
reading sources... [ 91%] topics/db/index
reading sources... [ 92%] topics/db/instrumentation
reading sources... [ 92%] topics/db/managers
reading sources... [ 92%] topics/db/models
reading sources... [ 92%] topics/db/multi-db
reading sources... [ 92%] topics/db/optimization
reading sources... [ 92%] topics/db/queries
reading sources... [ 93%] topics/db/search
reading sources... [ 93%] topics/db/sql
reading sources... [ 93%] topics/db/tablespaces
reading sources... [ 93%] topics/db/transactions
reading sources... [ 93%] topics/email
reading sources... [ 93%] topics/external-packages
reading sources... [ 94%] topics/files
reading sources... [ 94%] topics/forms/formsets
reading sources... [ 94%] topics/forms/index
reading sources... [ 94%] topics/forms/media
reading sources... [ 94%] topics/forms/modelforms
reading sources... [ 95%] topics/http/decorators
reading sources... [ 95%] topics/http/file-uploads
reading sources... [ 95%] topics/http/generic-views
reading sources... [ 95%] topics/http/index
reading sources... [ 95%] topics/http/middleware
reading sources... [ 95%] topics/http/sessions
reading sources... [ 96%] topics/http/shortcuts
reading sources... [ 96%] topics/http/urls
reading sources... [ 96%] topics/http/views
reading sources... [ 96%] topics/i18n/formatting
reading sources... [ 96%] topics/i18n/index
reading sources... [ 96%] topics/i18n/timezones
reading sources... [ 97%] topics/i18n/translation
reading sources... [ 97%] topics/index
reading sources... [ 97%] topics/install
reading sources... [ 97%] topics/logging
reading sources... [ 97%] topics/migrations
reading sources... [ 98%] topics/pagination
reading sources... [ 98%] topics/performance
reading sources... [ 98%] topics/security
reading sources... [ 98%] topics/serialization
reading sources... [ 98%] topics/settings
reading sources... [ 98%] topics/signals
reading sources... [ 99%] topics/signing
reading sources... [ 99%] topics/templates
reading sources... [ 99%] topics/testing/advanced
reading sources... [ 99%] topics/testing/index
reading sources... [ 99%] topics/testing/overview
reading sources... [100%] topics/testing/tools
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [ 0%] contents
writing output... [ 0%] faq/admin
writing output... [ 0%] faq/contributing
writing output... [ 0%] faq/general
writing output... [ 0%] faq/help
writing output... [ 1%] faq/index
writing output... [ 1%] faq/install
writing output... [ 1%] faq/models
writing output... [ 1%] faq/troubleshooting
writing output... [ 1%] faq/usage
writing output... [ 1%] glossary
writing output... [ 2%] howto/auth-remote-user
writing output... [ 2%] howto/csrf
writing output... [ 2%] howto/custom-file-storage
writing output... [ 2%] howto/custom-lookups
writing output... [ 2%] howto/custom-management-commands
writing output... [ 3%] howto/custom-model-fields
writing output... [ 3%] howto/custom-template-backend
writing output... [ 3%] howto/custom-template-tags
writing output... [ 3%] howto/deployment/asgi/daphne
writing output... [ 3%] howto/deployment/asgi/hypercorn
writing output... [ 3%] howto/deployment/asgi/index
writing output... [ 4%] howto/deployment/asgi/uvicorn
writing output... [ 4%] howto/deployment/checklist
writing output... [ 4%] howto/deployment/index
writing output... [ 4%] howto/deployment/wsgi/apache-auth
writing output... [ 4%] howto/deployment/wsgi/gunicorn
writing output... [ 4%] howto/deployment/wsgi/index
writing output... [ 5%] howto/deployment/wsgi/modwsgi
writing output... [ 5%] howto/deployment/wsgi/uwsgi
writing output... [ 5%] howto/error-reporting
writing output... [ 5%] howto/index
writing output... [ 5%] howto/initial-data
writing output... [ 6%] howto/legacy-databases
writing output... [ 6%] howto/logging
writing output... [ 6%] howto/outputting-csv
writing output... [ 6%] howto/outputting-pdf
writing output... [ 6%] howto/overriding-templates
writing output... [ 6%] howto/static-files/deployment
writing output... [ 7%] howto/static-files/index
writing output... [ 7%] howto/upgrade-version
writing output... [ 7%] howto/windows
writing output... [ 7%] howto/writing-migrations
writing output... [ 7%] index
writing output... [ 7%] internals/contributing/bugs-and-features
writing output... [ 8%] internals/contributing/committing-code
writing output... [ 8%] internals/contributing/index
writing output... [ 8%] internals/contributing/localizing
writing output... [ 8%] internals/contributing/new-contributors
writing output... [ 8%] internals/contributing/triaging-tickets
writing output... [ 9%] internals/contributing/writing-code/coding-style
writing output... [ 9%] internals/contributing/writing-code/index
writing output... [ 9%] internals/contributing/writing-code/javascript
writing output... [ 9%] internals/contributing/writing-code/submitting-patches
writing output... [ 9%] internals/contributing/writing-code/unit-tests
writing output... [ 9%] internals/contributing/writing-code/working-with-git
writing output... [ 10%] internals/contributing/writing-documentation
writing output... [ 10%] internals/deprecation
writing output... [ 10%] internals/git
writing output... [ 10%] internals/howto-release-django
writing output... [ 10%] internals/index
writing output... [ 10%] internals/mailing-lists
writing output... [ 11%] internals/organization
writing output... [ 11%] internals/release-process
writing output... [ 11%] internals/security
writing output... [ 11%] intro/contributing
writing output... [ 11%] intro/index
writing output... [ 12%] intro/install
writing output... [ 12%] intro/overview
writing output... [ 12%] intro/reusable-apps
writing output... [ 12%] intro/tutorial01
writing output... [ 12%] intro/tutorial02
writing output... [ 12%] intro/tutorial03
writing output... [ 13%] intro/tutorial04
writing output... [ 13%] intro/tutorial05
writing output... [ 13%] intro/tutorial06
writing output... [ 13%] intro/tutorial07
writing output... [ 13%] intro/tutorial08
writing output... [ 14%] intro/whatsnext
writing output... [ 14%] misc/api-stability
writing output... [ 14%] misc/design-philosophies
writing output... [ 14%] misc/distributions
writing output... [ 14%] misc/index
writing output... [ 14%] ref/applications
writing output... [ 15%] ref/checks
writing output... [ 15%] ref/class-based-views/base
writing output... [ 15%] ref/class-based-views/flattened-index
writing output... [ 15%] ref/class-based-views/generic-date-based
writing output... [ 15%] ref/class-based-views/generic-display
writing output... [ 15%] ref/class-based-views/generic-editing
writing output... [ 16%] ref/class-based-views/index
writing output... [ 16%] ref/class-based-views/mixins
writing output... [ 16%] ref/class-based-views/mixins-date-based
writing output... [ 16%] ref/class-based-views/mixins-editing
writing output... [ 16%] ref/class-based-views/mixins-multiple-object
writing output... [ 17%] ref/class-based-views/mixins-simple
writing output... [ 17%] ref/class-based-views/mixins-single-object
writing output... [ 17%] ref/clickjacking
writing output... [ 17%] ref/contrib/admin/actions
writing output... [ 17%] ref/contrib/admin/admindocs
writing output... [ 17%] ref/contrib/admin/filters
writing output... [ 18%] ref/contrib/admin/index
writing output... [ 18%] ref/contrib/admin/javascript
writing output... [ 18%] ref/contrib/auth
writing output... [ 18%] ref/contrib/contenttypes
writing output... [ 18%] ref/contrib/flatpages
writing output... [ 18%] ref/contrib/gis/admin
writing output... [ 19%] ref/contrib/gis/commands
writing output... [ 19%] ref/contrib/gis/db-api
writing output... [ 19%] ref/contrib/gis/deployment
writing output... [ 19%] ref/contrib/gis/feeds
writing output... [ 19%] ref/contrib/gis/forms-api
writing output... [ 20%] ref/contrib/gis/functions
writing output... [ 20%] ref/contrib/gis/gdal
writing output... [ 20%] ref/contrib/gis/geoip2
writing output... [ 20%] ref/contrib/gis/geoquerysets
writing output... [ 20%] ref/contrib/gis/geos
writing output... [ 20%] ref/contrib/gis/index
writing output... [ 21%] ref/contrib/gis/install/geolibs
writing output... [ 21%] ref/contrib/gis/install/index
writing output... [ 21%] ref/contrib/gis/install/postgis
writing output... [ 21%] ref/contrib/gis/install/spatialite
writing output... [ 21%] ref/contrib/gis/layermapping
writing output... [ 21%] ref/contrib/gis/measure
writing output... [ 22%] ref/contrib/gis/model-api
writing output... [ 22%] ref/contrib/gis/ogrinspect
writing output... [ 22%] ref/contrib/gis/serializers
writing output... [ 22%] ref/contrib/gis/sitemaps
writing output... [ 22%] ref/contrib/gis/testing
writing output... [ 23%] ref/contrib/gis/tutorial
writing output... [ 23%] ref/contrib/gis/utils
writing output... [ 23%] ref/contrib/humanize
writing output... [ 23%] ref/contrib/index
writing output... [ 23%] ref/contrib/messages
writing output... [ 23%] ref/contrib/postgres/aggregates
writing output... [ 24%] ref/contrib/postgres/constraints
writing output... [ 24%] ref/contrib/postgres/expressions
writing output... [ 24%] ref/contrib/postgres/fields
writing output... [ 24%] ref/contrib/postgres/forms
writing output... [ 24%] ref/contrib/postgres/functions
writing output... [ 25%] ref/contrib/postgres/index
writing output... [ 25%] ref/contrib/postgres/indexes
writing output... [ 25%] ref/contrib/postgres/lookups
writing output... [ 25%] ref/contrib/postgres/operations
writing output... [ 25%] ref/contrib/postgres/search
writing output... [ 25%] ref/contrib/postgres/validators
writing output... [ 26%] ref/contrib/redirects
writing output... [ 26%] ref/contrib/sitemaps
writing output... [ 26%] ref/contrib/sites
writing output... [ 26%] ref/contrib/staticfiles
writing output... [ 26%] ref/contrib/syndication
writing output... [ 26%] ref/csrf
writing output... [ 27%] ref/databases
writing output... [ 27%] ref/django-admin
writing output... [ 27%] ref/exceptions
writing output... [ 27%] ref/files/file
writing output... [ 27%] ref/files/index
writing output... [ 28%] ref/files/storage
writing output... [ 28%] ref/files/uploads
writing output... [ 28%] ref/forms/api
writing output... [ 28%] ref/forms/fields
writing output... [ 28%] ref/forms/formsets
writing output... [ 28%] ref/forms/index
writing output... [ 29%] ref/forms/models
writing output... [ 29%] ref/forms/renderers
writing output... [ 29%] ref/forms/validation
writing output... [ 29%] ref/forms/widgets
writing output... [ 29%] ref/index
writing output... [ 29%] ref/logging
writing output... [ 30%] ref/middleware
writing output... [ 30%] ref/migration-operations
writing output... [ 30%] ref/models/class
writing output... [ 30%] ref/models/conditional-expressions
writing output... [ 30%] ref/models/constraints
writing output... [ 31%] ref/models/database-functions
writing output... [ 31%] ref/models/expressions
writing output... [ 31%] ref/models/fields
writing output... [ 31%] ref/models/index
writing output... [ 31%] ref/models/indexes
writing output... [ 31%] ref/models/instances
writing output... [ 32%] ref/models/lookups
writing output... [ 32%] ref/models/meta
writing output... [ 32%] ref/models/options
writing output... [ 32%] ref/models/querysets
writing output... [ 32%] ref/models/relations
writing output... [ 32%] ref/paginator
writing output... [ 33%] ref/request-response
writing output... [ 33%] ref/schema-editor
writing output... [ 33%] ref/settings
writing output... [ 33%] ref/signals
writing output... [ 33%] ref/template-response
writing output... [ 34%] ref/templates/api
writing output... [ 34%] ref/templates/builtins
writing output... [ 34%] ref/templates/index
writing output... [ 34%] ref/templates/language
writing output... [ 34%] ref/unicode
writing output... [ 34%] ref/urlresolvers
writing output... [ 35%] ref/urls
writing output... [ 35%] ref/utils
writing output... [ 35%] ref/validators
writing output... [ 35%] ref/views
writing output... [ 35%] releases/0.95
writing output... [ 35%] releases/0.96
writing output... [ 36%] releases/1.0
writing output... [ 36%] releases/1.0-porting-guide
writing output... [ 36%] releases/1.0.1
writing output... [ 36%] releases/1.0.2
writing output... [ 36%] releases/1.1
writing output... [ 37%] releases/1.1.2
writing output... [ 37%] releases/1.1.3
writing output... [ 37%] releases/1.1.4
writing output... [ 37%] releases/1.10
writing output... [ 37%] releases/1.10.1
writing output... [ 37%] releases/1.10.2
writing output... [ 38%] releases/1.10.3
writing output... [ 38%] releases/1.10.4
writing output... [ 38%] releases/1.10.5
writing output... [ 38%] releases/1.10.6
writing output... [ 38%] releases/1.10.7
writing output... [ 39%] releases/1.10.8
writing output... [ 39%] releases/1.11
writing output... [ 39%] releases/1.11.1
writing output... [ 39%] releases/1.11.10
writing output... [ 39%] releases/1.11.11
writing output... [ 39%] releases/1.11.12
writing output... [ 40%] releases/1.11.13
writing output... [ 40%] releases/1.11.14
writing output... [ 40%] releases/1.11.15
writing output... [ 40%] releases/1.11.16
writing output... [ 40%] releases/1.11.17
writing output... [ 40%] releases/1.11.18
writing output... [ 41%] releases/1.11.19
writing output... [ 41%] releases/1.11.2
writing output... [ 41%] releases/1.11.20
writing output... [ 41%] releases/1.11.21
writing output... [ 41%] releases/1.11.22
writing output... [ 42%] releases/1.11.23
writing output... [ 42%] releases/1.11.24
writing output... [ 42%] releases/1.11.25
writing output... [ 42%] releases/1.11.26
writing output... [ 42%] releases/1.11.27
writing output... [ 42%] releases/1.11.28
writing output... [ 43%] releases/1.11.29
writing output... [ 43%] releases/1.11.3
writing output... [ 43%] releases/1.11.4
writing output... [ 43%] releases/1.11.5
writing output... [ 43%] releases/1.11.6
writing output... [ 43%] releases/1.11.7
writing output... [ 44%] releases/1.11.8
writing output... [ 44%] releases/1.11.9
writing output... [ 44%] releases/1.2
writing output... [ 44%] releases/1.2.1
writing output... [ 44%] releases/1.2.2
writing output... [ 45%] releases/1.2.3
writing output... [ 45%] releases/1.2.4
writing output... [ 45%] releases/1.2.5
writing output... [ 45%] releases/1.2.6
writing output... [ 45%] releases/1.2.7
writing output... [ 45%] releases/1.3
writing output... [ 46%] releases/1.3.1
writing output... [ 46%] releases/1.3.2
writing output... [ 46%] releases/1.3.3
writing output... [ 46%] releases/1.3.4
writing output... [ 46%] releases/1.3.5
writing output... [ 46%] releases/1.3.6
writing output... [ 47%] releases/1.3.7
writing output... [ 47%] releases/1.4
writing output... [ 47%] releases/1.4.1
writing output... [ 47%] releases/1.4.10
writing output... [ 47%] releases/1.4.11
writing output... [ 48%] releases/1.4.12
writing output... [ 48%] releases/1.4.13
writing output... [ 48%] releases/1.4.14
writing output... [ 48%] releases/1.4.15
writing output... [ 48%] releases/1.4.16
writing output... [ 48%] releases/1.4.17
writing output... [ 49%] releases/1.4.18
writing output... [ 49%] releases/1.4.19
writing output... [ 49%] releases/1.4.2
writing output... [ 49%] releases/1.4.20
writing output... [ 49%] releases/1.4.21
writing output... [ 50%] releases/1.4.22
writing output... [ 50%] releases/1.4.3
writing output... [ 50%] releases/1.4.4
writing output... [ 50%] releases/1.4.5
writing output... [ 50%] releases/1.4.6
writing output... [ 50%] releases/1.4.7
writing output... [ 51%] releases/1.4.8
writing output... [ 51%] releases/1.4.9
writing output... [ 51%] releases/1.5
writing output... [ 51%] releases/1.5.1
writing output... [ 51%] releases/1.5.10
writing output... [ 51%] releases/1.5.11
writing output... [ 52%] releases/1.5.12
writing output... [ 52%] releases/1.5.2
writing output... [ 52%] releases/1.5.3
writing output... [ 52%] releases/1.5.4
writing output... [ 52%] releases/1.5.5
writing output... [ 53%] releases/1.5.6
writing output... [ 53%] releases/1.5.7
writing output... [ 53%] releases/1.5.8
writing output... [ 53%] releases/1.5.9
writing output... [ 53%] releases/1.6
writing output... [ 53%] releases/1.6.1
writing output... [ 54%] releases/1.6.10
writing output... [ 54%] releases/1.6.11
writing output... [ 54%] releases/1.6.2
writing output... [ 54%] releases/1.6.3
writing output... [ 54%] releases/1.6.4
writing output... [ 54%] releases/1.6.5
writing output... [ 55%] releases/1.6.6
writing output... [ 55%] releases/1.6.7
writing output... [ 55%] releases/1.6.8
writing output... [ 55%] releases/1.6.9
writing output... [ 55%] releases/1.7
writing output... [ 56%] releases/1.7.1
writing output... [ 56%] releases/1.7.10
writing output... [ 56%] releases/1.7.11
writing output... [ 56%] releases/1.7.2
writing output... [ 56%] releases/1.7.3
writing output... [ 56%] releases/1.7.4
writing output... [ 57%] releases/1.7.5
writing output... [ 57%] releases/1.7.6
writing output... [ 57%] releases/1.7.7
writing output... [ 57%] releases/1.7.8
writing output... [ 57%] releases/1.7.9
writing output... [ 57%] releases/1.8
writing output... [ 58%] releases/1.8.1
writing output... [ 58%] releases/1.8.10
writing output... [ 58%] releases/1.8.11
writing output... [ 58%] releases/1.8.12
writing output... [ 58%] releases/1.8.13
writing output... [ 59%] releases/1.8.14
writing output... [ 59%] releases/1.8.15
writing output... [ 59%] releases/1.8.16
writing output... [ 59%] releases/1.8.17
writing output... [ 59%] releases/1.8.18
writing output... [ 59%] releases/1.8.19
writing output... [ 60%] releases/1.8.2
writing output... [ 60%] releases/1.8.3
writing output... [ 60%] releases/1.8.4
writing output... [ 60%] releases/1.8.5
writing output... [ 60%] releases/1.8.6
writing output... [ 60%] releases/1.8.7
writing output... [ 61%] releases/1.8.8
writing output... [ 61%] releases/1.8.9
writing output... [ 61%] releases/1.9
writing output... [ 61%] releases/1.9.1
writing output... [ 61%] releases/1.9.10
writing output... [ 62%] releases/1.9.11
writing output... [ 62%] releases/1.9.12
writing output... [ 62%] releases/1.9.13
writing output... [ 62%] releases/1.9.2
writing output... [ 62%] releases/1.9.3
writing output... [ 62%] releases/1.9.4
writing output... [ 63%] releases/1.9.5
writing output... [ 63%] releases/1.9.6
writing output... [ 63%] releases/1.9.7
writing output... [ 63%] releases/1.9.8
writing output... [ 63%] releases/1.9.9
writing output... [ 64%] releases/2.0
writing output... [ 64%] releases/2.0.1
writing output... [ 64%] releases/2.0.10
writing output... [ 64%] releases/2.0.11
writing output... [ 64%] releases/2.0.12
writing output... [ 64%] releases/2.0.13
writing output... [ 65%] releases/2.0.2
writing output... [ 65%] releases/2.0.3
writing output... [ 65%] releases/2.0.4
writing output... [ 65%] releases/2.0.5
writing output... [ 65%] releases/2.0.6
writing output... [ 65%] releases/2.0.7
writing output... [ 66%] releases/2.0.8
writing output... [ 66%] releases/2.0.9
writing output... [ 66%] releases/2.1
writing output... [ 66%] releases/2.1.1
writing output... [ 66%] releases/2.1.10
writing output... [ 67%] releases/2.1.11
writing output... [ 67%] releases/2.1.12
writing output... [ 67%] releases/2.1.13
writing output... [ 67%] releases/2.1.14
writing output... [ 67%] releases/2.1.15
writing output... [ 67%] releases/2.1.2
writing output... [ 68%] releases/2.1.3
writing output... [ 68%] releases/2.1.4
writing output... [ 68%] releases/2.1.5
writing output... [ 68%] releases/2.1.6
writing output... [ 68%] releases/2.1.7
writing output... [ 68%] releases/2.1.8
writing output... [ 69%] releases/2.1.9
writing output... [ 69%] releases/2.2
writing output... [ 69%] releases/2.2.1
writing output... [ 69%] releases/2.2.10
writing output... [ 69%] releases/2.2.11
writing output... [ 70%] releases/2.2.12
writing output... [ 70%] releases/2.2.13
writing output... [ 70%] releases/2.2.14
writing output... [ 70%] releases/2.2.15
writing output... [ 70%] releases/2.2.16
writing output... [ 70%] releases/2.2.17
writing output... [ 71%] releases/2.2.18
writing output... [ 71%] releases/2.2.19
writing output... [ 71%] releases/2.2.2
writing output... [ 71%] releases/2.2.20
writing output... [ 71%] releases/2.2.21
writing output... [ 71%] releases/2.2.22
writing output... [ 72%] releases/2.2.23
writing output... [ 72%] releases/2.2.24
writing output... [ 72%] releases/2.2.25
writing output... [ 72%] releases/2.2.26
writing output... [ 72%] releases/2.2.27
writing output... [ 73%] releases/2.2.28
writing output... [ 73%] releases/2.2.3
writing output... [ 73%] releases/2.2.4
writing output... [ 73%] releases/2.2.5
writing output... [ 73%] releases/2.2.6
writing output... [ 73%] releases/2.2.7
writing output... [ 74%] releases/2.2.8
writing output... [ 74%] releases/2.2.9
writing output... [ 74%] releases/3.0
writing output... [ 74%] releases/3.0.1
writing output... [ 74%] releases/3.0.10
writing output... [ 75%] releases/3.0.11
writing output... [ 75%] releases/3.0.12
writing output... [ 75%] releases/3.0.13
writing output... [ 75%] releases/3.0.14
writing output... [ 75%] releases/3.0.2
writing output... [ 75%] releases/3.0.3
writing output... [ 76%] releases/3.0.4
writing output... [ 76%] releases/3.0.5
writing output... [ 76%] releases/3.0.6
writing output... [ 76%] releases/3.0.7
writing output... [ 76%] releases/3.0.8
writing output... [ 76%] releases/3.0.9
writing output... [ 77%] releases/3.1
writing output... [ 77%] releases/3.1.1
writing output... [ 77%] releases/3.1.10
writing output... [ 77%] releases/3.1.11
writing output... [ 77%] releases/3.1.12
writing output... [ 78%] releases/3.1.13
writing output... [ 78%] releases/3.1.14
writing output... [ 78%] releases/3.1.2
writing output... [ 78%] releases/3.1.3
writing output... [ 78%] releases/3.1.4
writing output... [ 78%] releases/3.1.5
writing output... [ 79%] releases/3.1.6
writing output... [ 79%] releases/3.1.7
writing output... [ 79%] releases/3.1.8
writing output... [ 79%] releases/3.1.9
writing output... [ 79%] releases/3.2
writing output... [ 79%] releases/3.2.1
writing output... [ 80%] releases/3.2.10
writing output... [ 80%] releases/3.2.11
writing output... [ 80%] releases/3.2.12
writing output... [ 80%] releases/3.2.13
writing output... [ 80%] releases/3.2.14
writing output... [ 81%] releases/3.2.15
writing output... [ 81%] releases/3.2.16
writing output... [ 81%] releases/3.2.17
writing output... [ 81%] releases/3.2.18
writing output... [ 81%] releases/3.2.19
writing output... [ 81%] releases/3.2.2
writing output... [ 82%] releases/3.2.20
writing output... [ 82%] releases/3.2.3
writing output... [ 82%] releases/3.2.4
writing output... [ 82%] releases/3.2.5
writing output... [ 82%] releases/3.2.6
writing output... [ 82%] releases/3.2.7
writing output... [ 83%] releases/3.2.8
writing output... [ 83%] releases/3.2.9
writing output... [ 83%] releases/4.0
writing output... [ 83%] releases/4.0.1
writing output... [ 83%] releases/4.0.10
writing output... [ 84%] releases/4.0.2
writing output... [ 84%] releases/4.0.3
writing output... [ 84%] releases/4.0.4
writing output... [ 84%] releases/4.0.5
writing output... [ 84%] releases/4.0.6
writing output... [ 84%] releases/4.0.7
writing output... [ 85%] releases/4.0.8
writing output... [ 85%] releases/4.0.9
writing output... [ 85%] releases/4.1
writing output... [ 85%] releases/4.1.1
writing output... [ 85%] releases/4.1.10
writing output... [ 85%] releases/4.1.2
writing output... [ 86%] releases/4.1.3
writing output... [ 86%] releases/4.1.4
writing output... [ 86%] releases/4.1.5
writing output... [ 86%] releases/4.1.6
writing output... [ 86%] releases/4.1.7
writing output... [ 87%] releases/4.1.8
writing output... [ 87%] releases/4.1.9
writing output... [ 87%] releases/4.2
writing output... [ 87%] releases/4.2.1
writing output... [ 87%] releases/4.2.2
writing output... [ 87%] releases/4.2.3
writing output... [ 88%] releases/index
writing output... [ 88%] releases/security
writing output... [ 88%] topics/async
writing output... [ 88%] topics/auth/customizing
writing output... [ 88%] topics/auth/default
writing output... [ 89%] topics/auth/index
writing output... [ 89%] topics/auth/passwords
writing output... [ 89%] topics/cache
writing output... [ 89%] topics/checks
writing output... [ 89%] topics/class-based-views/generic-display
writing output... [ 89%] topics/class-based-views/generic-editing
writing output... [ 90%] topics/class-based-views/index
writing output... [ 90%] topics/class-based-views/intro
writing output... [ 90%] topics/class-based-views/mixins
writing output... [ 90%] topics/conditional-view-processing
writing output... [ 90%] topics/db/aggregation
writing output... [ 90%] topics/db/examples/index
writing output... [ 91%] topics/db/examples/many_to_many
writing output... [ 91%] topics/db/examples/many_to_one
writing output... [ 91%] topics/db/examples/one_to_one
writing output... [ 91%] topics/db/fixtures
writing output... [ 91%] topics/db/index
writing output... [ 92%] topics/db/instrumentation
writing output... [ 92%] topics/db/managers
writing output... [ 92%] topics/db/models
writing output... [ 92%] topics/db/multi-db
writing output... [ 92%] topics/db/optimization
writing output... [ 92%] topics/db/queries
writing output... [ 93%] topics/db/search
writing output... [ 93%] topics/db/sql
writing output... [ 93%] topics/db/tablespaces
writing output... [ 93%] topics/db/transactions
writing output... [ 93%] topics/email
writing output... [ 93%] topics/external-packages
writing output... [ 94%] topics/files
writing output... [ 94%] topics/forms/formsets
writing output... [ 94%] topics/forms/index
writing output... [ 94%] topics/forms/media
writing output... [ 94%] topics/forms/modelforms
writing output... [ 95%] topics/http/decorators
writing output... [ 95%] topics/http/file-uploads
writing output... [ 95%] topics/http/generic-views
writing output... [ 95%] topics/http/index
writing output... [ 95%] topics/http/middleware
writing output... [ 95%] topics/http/sessions
writing output... [ 96%] topics/http/shortcuts
writing output... [ 96%] topics/http/urls
writing output... [ 96%] topics/http/views
writing output... [ 96%] topics/i18n/formatting
writing output... [ 96%] topics/i18n/index
writing output... [ 96%] topics/i18n/timezones
writing output... [ 97%] topics/i18n/translation
writing output... [ 97%] topics/index
writing output... [ 97%] topics/install
writing output... [ 97%] topics/logging
writing output... [ 97%] topics/migrations
writing output... [ 98%] topics/pagination
writing output... [ 98%] topics/performance
writing output... [ 98%] topics/security
writing output... [ 98%] topics/serialization
writing output... [ 98%] topics/settings
writing output... [ 98%] topics/signals
writing output... [ 99%] topics/signing
writing output... [ 99%] topics/templates
writing output... [ 99%] topics/testing/advanced
writing output... [ 99%] topics/testing/index
writing output... [ 99%] topics/testing/overview
writing output... [100%] topics/testing/tools
/builddir/build/BUILD/Django-4.2.3/docs/howto/custom-management-commands.txt:122: WARNING: py:mod reference target not found: argparse
/builddir/build/BUILD/Django-4.2.3/docs/howto/custom-management-commands.txt:208: WARNING: py:mod reference target not found: argparse
/builddir/build/BUILD/Django-4.2.3/docs/howto/custom-management-commands.txt:270: WARNING: py:class reference target not found: argparse.ArgumentParser
/builddir/build/BUILD/Django-4.2.3/docs/howto/custom-management-commands.txt:274: WARNING: py:class reference target not found: argparse.ArgumentParser
/builddir/build/BUILD/Django-4.2.3/docs/howto/custom-management-commands.txt:365: WARNING: py:func reference target not found: sys.exit
/builddir/build/BUILD/Django-4.2.3/docs/howto/custom-template-tags.txt:373: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/howto/custom-template-tags.txt:670: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/howto/deployment/wsgi/modwsgi.txt:51: WARNING: py:mod reference target not found: venv
/builddir/build/BUILD/Django-4.2.3/docs/howto/error-reporting.txt:343: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/howto/error-reporting.txt:349: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:27: WARNING: py:func reference target not found: logging.getLogger
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:46: WARNING: py:class reference target not found: logging.LogRecord
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:74: WARNING: py:class reference target not found: logging.LogRecord
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:77: WARNING: undefined label: 'logging-config-dictschema'
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:85: WARNING: py:mod reference target not found: python:logging.config
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:112: WARNING: py:class reference target not found: logging.FileHandler
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:129: WARNING: py:mod reference target not found: logging.handlers
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:189: WARNING: py:class reference target not found: logging.LogRecord
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:211: WARNING: py:meth reference target not found: str.format
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:211: WARNING: py:class reference target not found: string.Template
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:214: WARNING: undefined label: 'logrecord-attributes'
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:214: WARNING: py:class reference target not found: logging.LogRecord
/builddir/build/BUILD/Django-4.2.3/docs/howto/logging.txt:240: WARNING: py:func reference target not found: logging.getLogger
/builddir/build/BUILD/Django-4.2.3/docs/howto/outputting-csv.txt:12: WARNING: py:mod reference target not found: csv
/builddir/build/BUILD/Django-4.2.3/docs/howto/outputting-csv.txt:12: WARNING: py:mod reference target not found: csv
/builddir/build/BUILD/Django-4.2.3/docs/howto/outputting-csv.txt:51: WARNING: term not in glossary: 'iterable'
/builddir/build/BUILD/Django-4.2.3/docs/howto/outputting-csv.txt:104: WARNING: py:mod reference target not found: csv
/builddir/build/BUILD/Django-4.2.3/docs/howto/upgrade-version.txt:62: WARNING: 'envvar' reference target not found: PYTHONWARNINGS
/builddir/build/BUILD/Django-4.2.3/docs/howto/upgrade-version.txt:89: WARNING: py:mod reference target not found: venv
/builddir/build/BUILD/Django-4.2.3/docs/howto/windows.txt:38: WARNING: unknown document: 'python:using/windows'
/builddir/build/BUILD/Django-4.2.3/docs/howto/windows.txt:53: WARNING: unknown document: 'python:tutorial/venv'
/builddir/build/BUILD/Django-4.2.3/docs/howto/windows.txt:134: WARNING: 'envvar' reference target not found: PYTHONUTF8
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:62: WARNING: undefined label: 'old-string-formatting'
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:62: WARNING: undefined label: 'f-strings'
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:62: WARNING: py:meth reference target not found: str.format
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertRaises
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertWarns
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertRaisesRegex
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:103: WARNING: py:meth reference target not found: unittest.TestCase.assertWarnsRegex
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:112: WARNING: py:meth reference target not found: unittest.TestCase.assertIs
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:112: WARNING: py:meth reference target not found: unittest.TestCase.assertTrue
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/coding-style.txt:112: WARNING: py:meth reference target not found: unittest.TestCase.assertFalse
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-code/unit-tests.txt:165: WARNING: 'envvar' reference target not found: PYTHONPATH
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:60: WARNING: undefined label: 'sphinx:rst-index'
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:218: WARNING: py:mod reference target not found: sphinx.ext.intersphinx
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:250: WARNING: rst:role reference target not found: rfc
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:254: WARNING: rst:role reference target not found: pep
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:258: WARNING: rst:role reference target not found: mimetype
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:261: WARNING: rst:role reference target not found: envvar
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:261: WARNING: rst:dir reference target not found: envvar
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:273: WARNING: undefined label: 'sphinx:rst-index'
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:501: WARNING: rst:role reference target not found: doc
/builddir/build/BUILD/Django-4.2.3/docs/internals/contributing/writing-documentation.txt:501: WARNING: rst:role reference target not found: ref
/builddir/build/BUILD/Django-4.2.3/docs/internals/deprecation.txt:598: WARNING: py:mod reference target not found: optparse
/builddir/build/BUILD/Django-4.2.3/docs/internals/deprecation.txt:598: WARNING: py:mod reference target not found: argparse
/builddir/build/BUILD/Django-4.2.3/docs/internals/deprecation.txt:793: WARNING: py:class reference target not found: collections.OrderedDict
/builddir/build/BUILD/Django-4.2.3/docs/internals/deprecation.txt:977: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/internals/deprecation.txt:1011: WARNING: py:class reference target not found: warnings.catch_warnings
/builddir/build/BUILD/Django-4.2.3/docs/internals/deprecation.txt:1135: WARNING: py:class reference target not found: unittest.TextTestRunner
/builddir/build/BUILD/Django-4.2.3/docs/intro/contributing.txt:345: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/intro/reusable-apps.txt:36: WARNING: term not in glossary: 'package'
/builddir/build/BUILD/Django-4.2.3/docs/intro/reusable-apps.txt:336: WARNING: unknown document: 'python:tutorial/venv'
/builddir/build/BUILD/Django-4.2.3/docs/intro/tutorial01.txt:105: WARNING: undefined label: 'tut-packages'
/builddir/build/BUILD/Django-4.2.3/docs/intro/tutorial01.txt:217: WARNING: undefined label: 'tut-searchpath'
/builddir/build/BUILD/Django-4.2.3/docs/intro/tutorial02.txt:468: WARNING: py:mod reference target not found: datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:52: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:132: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:137: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:140: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:145: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:224: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:229: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:232: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:237: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:326: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:329: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:334: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:343: WARNING: py:func reference target not found: time.strptime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strptime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:404: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:443: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:446: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:451: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:456: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/generic-date-based.txt:461: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:9: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:25: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:35: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:77: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:87: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:129: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:139: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:181: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/class-based-views/mixins-date-based.txt:193: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/admin/index.txt:2829: WARNING: py:class reference target not found: weakref.WeakSet
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/gis/gdal.txt:1231: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/gis/gdal.txt:1287: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/gis/geoip2.txt:161: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/gis/install/index.txt:441: WARNING: unknown document: 'python:tutorial/venv'
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/gis/install/index.txt:457: WARNING: py:func reference target not found: ctypes.util.find_library
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/gis/tutorial.txt:324: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/index.txt:5: WARNING: undefined label: 'tut-batteries-included'
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/postgres/fields.txt:582: WARNING: undefined label: 'psycopg:adapt-range'
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/postgres/fields.txt:915: WARNING: py:func reference target not found: psycopg:psycopg.types.range.register_range
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/sitemaps.txt:124: WARNING: term not in glossary: 'sequence'
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/sitemaps.txt:129: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/sitemaps.txt:144: WARNING: term not in glossary: 'sequence'
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/sitemaps.txt:179: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/sitemaps.txt:183: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/sitemaps.txt:278: WARNING: term not in glossary: 'sequence'
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/staticfiles.txt:495: WARNING: py:mod reference target not found: mimetypes
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/syndication.txt:1001: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/syndication.txt:1002: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/contrib/syndication.txt:1065: WARNING: py:class reference target not found: xml.sax.saxutils.XMLGenerator
/builddir/build/BUILD/Django-4.2.3/docs/ref/databases.txt:262: WARNING: undefined label: 'psycopg:client-side-binding-cursors'
/builddir/build/BUILD/Django-4.2.3/docs/ref/databases.txt:262: WARNING: undefined label: 'psycopg:server-side-binding'
/builddir/build/BUILD/Django-4.2.3/docs/ref/databases.txt:306: WARNING: undefined label: 'psycopg:server-side-cursors'
/builddir/build/BUILD/Django-4.2.3/docs/ref/databases.txt:911: WARNING: py:mod reference target not found: sqlite3
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:188: WARNING: py:mod reference target not found: glob
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:643: WARNING: py:mod reference target not found: glob
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:731: WARNING: undefined label: 'python:identifiers'
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1092: WARNING: 'envvar' reference target not found: PYTHONSTARTUP
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1113: WARNING: py:func reference target not found: select.select
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1482: WARNING: py:func reference target not found: multiprocessing.cpu_count
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1488: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1512: WARNING: py:mod reference target not found: pdb
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1523: WARNING: undefined label: 'python:pickle-picklable'
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1541: WARNING: unknown option: 'unittest.-k'
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1551: WARNING: unknown option: 'unittest.-b'
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1556: WARNING: py:func reference target not found: faulthandler.enable
/builddir/build/BUILD/Django-4.2.3/docs/ref/django-admin.txt:1811: WARNING: 'envvar' reference target not found: PYTHONPATH
/builddir/build/BUILD/Django-4.2.3/docs/ref/exceptions.txt:349: WARNING: undefined label: 'bltin-exceptions'
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/file.txt:15: WARNING: term not in glossary: 'file object'
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/file.txt:32: WARNING: term not in glossary: 'file object'
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/file.txt:36: WARNING: term not in glossary: 'file object'
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/file.txt:51: WARNING: py:func reference target not found: python:open
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/storage.txt:83: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/storage.txt:83: WARNING: py:func reference target not found: os.path.getctime
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/storage.txt:150: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/storage.txt:179: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/storage.txt:188: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/files/storage.txt:210: WARNING: py:mod reference target not found: os.path
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:443: WARNING: term not in glossary: 'iterable'
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:572: WARNING: py:class reference target not found: python:datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:573: WARNING: py:attr reference target not found: datetime.timedelta.min
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:573: WARNING: py:attr reference target not found: datetime.timedelta.max
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:862: WARNING: py:class reference target not found: json.JSONEncoder
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:862: WARNING: py:class reference target not found: python:uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:871: WARNING: py:class reference target not found: json.JSONDecoder
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:877: WARNING: py:class reference target not found: json.JSONDecodeError
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:1092: WARNING: py:class reference target not found: python:uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/fields.txt:1095: WARNING: py:class reference target not found: python:uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/widgets.txt:258: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/widgets.txt:258: WARNING: py:class reference target not found: datetime.time
/builddir/build/BUILD/Django-4.2.3/docs/ref/forms/widgets.txt:413: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/logging.txt:15: WARNING: py:mod reference target not found: logging
/builddir/build/BUILD/Django-4.2.3/docs/ref/logging.txt:25: WARNING: undefined label: 'logging-config-dictschema'
/builddir/build/BUILD/Django-4.2.3/docs/ref/logging.txt:264: WARNING: py:mod reference target not found: python:logging.handlers
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:7: WARNING: unknown keyword: 'if'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:7: WARNING: unknown keyword: 'elif'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:7: WARNING: unknown keyword: 'else'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:106: WARNING: unknown keyword: 'if'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:106: WARNING: unknown keyword: 'elif'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:106: WARNING: unknown keyword: 'else'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:169: WARNING: unknown keyword: 'if'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:169: WARNING: unknown keyword: 'elif'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/conditional-expressions.txt:169: WARNING: unknown keyword: 'else'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/database-functions.txt:250: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/database-functions.txt:582: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/database-functions.txt:1454: WARNING: py:func reference target not found: chr
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/database-functions.txt:1623: WARNING: py:func reference target not found: ord
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/expressions.txt:525: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/expressions.txt:544: WARNING: unknown keyword: 'if'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/expressions.txt:544: WARNING: unknown keyword: 'elif'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/expressions.txt:544: WARNING: unknown keyword: 'else'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/expressions.txt:1031: WARNING: py:data reference target not found: NotImplemented
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:89: WARNING: term not in glossary: 'sequence'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:223: WARNING: py:mod reference target not found: enum
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:245: WARNING: py:func reference target not found: enum.unique
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:296: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:699: WARNING: py:meth reference target not found: datetime.date.today
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:743: WARNING: py:class reference target not found: decimal.Decimal
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:785: WARNING: py:class reference target not found: python:datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:823: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:823: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:904: WARNING: py:func reference target not found: time.strftime
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:1143: WARNING: py:mod reference target not found: decimal
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:1246: WARNING: py:class reference target not found: json.JSONEncoder
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:1246: WARNING: py:class reference target not found: python:uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:1255: WARNING: py:class reference target not found: json.JSONDecoder
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:1427: WARNING: py:class reference target not found: python:uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/fields.txt:2153: WARNING: undefined label: 'descriptors'
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/indexes.txt:163: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/instances.txt:716: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/instances.txt:810: WARNING: py:meth reference target not found: object.__hash__
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:99: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:784: WARNING: py:func reference target not found: python:collections.namedtuple
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:847: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:851: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:889: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:895: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:902: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/models/querysets.txt:3730: WARNING: py:class reference target not found: datetime.time
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:448: WARNING: py:class reference target not found: xml.etree.ElementTree.ElementTree
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:535: WARNING: py:meth reference target not found: dict.setdefault
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:539: WARNING: py:meth reference target not found: dict.update
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:554: WARNING: py:meth reference target not found: dict.items
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:566: WARNING: py:meth reference target not found: dict.values
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:580: WARNING: py:func reference target not found: copy.deepcopy
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:847: WARNING: py:class reference target not found: http.HTTPStatus
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:886: WARNING: py:meth reference target not found: dict.items
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:894: WARNING: py:class reference target not found: http.cookies.Morsel
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:897: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/ref/request-response.txt:1073: WARNING: py:class reference target not found: http.HTTPStatus
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:1170: WARNING: undefined label: 'strftime-strptime-behavior'
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:1214: WARNING: undefined label: 'strftime-strptime-behavior'
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:1568: WARNING: py:func reference target not found: python:ssl.wrap_socket
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:1637: WARNING: py:func reference target not found: os.chmod
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:2085: WARNING: undefined label: 'logging-config-dictschema'
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:2857: WARNING: undefined label: 'strftime-strptime-behavior'
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:2893: WARNING: py:func reference target not found: time.tzset
/builddir/build/BUILD/Django-4.2.3/docs/ref/settings.txt:2917: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/templates/builtins.txt:1014: WARNING: py:func reference target not found: collections.namedtuple
/builddir/build/BUILD/Django-4.2.3/docs/ref/templates/builtins.txt:1023: WARNING: py:func reference target not found: collections.namedtuple
/builddir/build/BUILD/Django-4.2.3/docs/ref/templates/builtins.txt:1612: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/templates/builtins.txt:1628: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/templates/builtins.txt:2342: WARNING: py:func reference target not found: pprint.pprint
/builddir/build/BUILD/Django-4.2.3/docs/ref/templates/builtins.txt:2452: WARNING: undefined label: 'old-string-formatting'
/builddir/build/BUILD/Django-4.2.3/docs/ref/templates/builtins.txt:2530: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/unicode.txt:156: WARNING: py:func reference target not found: urllib.parse.quote
/builddir/build/BUILD/Django-4.2.3/docs/ref/unicode.txt:156: WARNING: py:func reference target not found: urllib.parse.quote_plus
/builddir/build/BUILD/Django-4.2.3/docs/ref/urlresolvers.txt:79: WARNING: py:func reference target not found: urllib.parse.quote
/builddir/build/BUILD/Django-4.2.3/docs/ref/urls.txt:65: WARNING: py:mod reference target not found: re
/builddir/build/BUILD/Django-4.2.3/docs/ref/urls.txt:75: WARNING: py:func reference target not found: re.fullmatch
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:113: WARNING: py:mod reference target not found: datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:124: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:128: WARNING: py:class reference target not found: datetime.time
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:135: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:137: WARNING: py:class reference target not found: datetime.timezone
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:142: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:280: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:490: WARNING: undefined label: 'descriptor-invocation'
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:523: WARNING: py:func reference target not found: classmethod
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:619: WARNING: py:meth reference target not found: str.format
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:733: WARNING: py:func reference target not found: urllib.parse.urlencode
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:846: WARNING: py:meth reference target not found: str.format
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:900: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:904: WARNING: py:attr reference target not found: datetime.timezone.utc
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:904: WARNING: py:attr reference target not found: datetime.timezone.utc
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:909: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:912: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:918: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:928: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:938: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:958: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:968: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:968: WARNING: py:meth reference target not found: datetime.datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:978: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:995: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:1000: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:1005: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:1005: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:1037: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/utils.txt:1037: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/ref/validators.txt:89: WARNING: py:func reference target not found: re.search
/builddir/build/BUILD/Django-4.2.3/docs/ref/validators.txt:99: WARNING: py:func reference target not found: re.search
/builddir/build/BUILD/Django-4.2.3/docs/ref/validators.txt:99: WARNING: py:func reference target not found: re.compile
/builddir/build/BUILD/Django-4.2.3/docs/ref/validators.txt:122: WARNING: undefined label: 'python:contents-of-module-re'
/builddir/build/BUILD/Django-4.2.3/docs/releases/0.96.txt:207: WARNING: py:mod reference target not found: doctest
/builddir/build/BUILD/Django-4.2.3/docs/releases/0.96.txt:207: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.10.txt:447: WARNING: py:class reference target not found: io.TextIOWrapper
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.11.txt:285: WARNING: py:class reference target not found: io.TextIOWrapper
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.11.txt:392: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.11.txt:428: WARNING: py:meth reference target not found: python:unittest.TestCase.subTest
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.11.txt:777: WARNING: py:class reference target not found: io.StringIO
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.11.txt:777: WARNING: py:class reference target not found: io.BytesIO
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.2.txt:769: WARNING: py:mod reference target not found: warnings
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.3.txt:662: WARNING: py:mod reference target not found: warnings
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.4.txt:661: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.4.txt:851: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.4.txt:851: WARNING: py:class reference target not found: datetime.time
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.4.12.txt:12: WARNING: py:func reference target not found: functools.partial
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:391: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:483: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:495: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:499: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:515: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:521: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:608: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:773: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:773: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:778: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.txt:794: WARNING: py:func reference target not found: itertools.product
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.3.txt:31: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.3.txt:42: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.3.txt:42: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.3.txt:42: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.5.7.txt:12: WARNING: py:func reference target not found: functools.partial
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:207: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:423: WARNING: undefined label: 'doctest-unittest-api'
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:427: WARNING: py:mod reference target not found: doctest
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:504: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:504: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:508: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:804: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:815: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:815: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.txt:815: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.6.4.txt:16: WARNING: py:func reference target not found: functools.partial
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.7.txt:1051: WARNING: 'envvar' reference target not found: PYTHONPATH
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.7.txt:1479: WARNING: py:mod reference target not found: logging.config
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.7.txt:1479: WARNING: py:mod reference target not found: importlib
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.7.txt:1497: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.7.txt:1506: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.7.txt:1506: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.7.txt:1515: WARNING: py:class reference target not found: collections.OrderedDict
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:90: WARNING: py:class reference target not found: python:datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:108: WARNING: unknown keyword: 'if'
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:108: WARNING: unknown keyword: 'elif'
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:108: WARNING: unknown keyword: 'else'
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:274: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:381: WARNING: py:meth reference target not found: str.format
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:427: WARNING: py:mod reference target not found: argparse
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:747: WARNING: py:mod reference target not found: argparse
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:760: WARNING: py:mod reference target not found: optparse
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:760: WARNING: py:class reference target not found: argparse.ArgumentParser
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:1401: WARNING: py:mod reference target not found: argparse
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.txt:1401: WARNING: py:mod reference target not found: optparse
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.8.1.txt:13: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.9.txt:696: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.9.txt:701: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.9.txt:877: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.9.txt:889: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.9.txt:900: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/1.9.txt:1066: WARNING: py:data reference target not found: http.client.responses
/builddir/build/BUILD/Django-4.2.3/docs/releases/2.0.txt:347: WARNING: unknown option: '-b'
/builddir/build/BUILD/Django-4.2.3/docs/releases/2.1.txt:228: WARNING: py:meth reference target not found: unittest.TestCase.assertWarnsRegex
/builddir/build/BUILD/Django-4.2.3/docs/releases/2.2.txt:505: WARNING: py:class reference target not found: datetime.timezone
/builddir/build/BUILD/Django-4.2.3/docs/releases/2.2.1.txt:29: WARNING: py:class reference target not found: python:range
/builddir/build/BUILD/Django-4.2.3/docs/releases/2.2.19.txt:12: WARNING: py:func reference target not found: urllib.parse.parse_qsl
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:162: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:164: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:286: WARNING: undefined label: 'descriptors'
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:304: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:421: WARNING: py:class reference target not found: datetime.timezone
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:421: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:482: WARNING: py:meth reference target not found: unittest.TestCase.assertLogs
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:485: WARNING: py:func reference target not found: functools.lru_cache
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:491: WARNING: py:class reference target not found: contextlib.ContextDecorator
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:494: WARNING: py:func reference target not found: os.path.abspath
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:505: WARNING: py:func reference target not found: functools.partial
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:505: WARNING: py:class reference target not found: functools.partialmethod
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:546: WARNING: py:func reference target not found: html.escape
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:550: WARNING: unknown option: 'unittest.-k'
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:555: WARNING: py:func reference target not found: urllib.parse.urlencode
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.quote
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.quote_plus
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.unquote
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:597: WARNING: py:func reference target not found: urllib.parse.unquote_plus
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.txt:616: WARNING: py:func reference target not found: html.unescape
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.0.13.txt:12: WARNING: py:func reference target not found: urllib.parse.parse_qsl
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:256: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:279: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:304: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:410: WARNING: py:meth reference target not found: sqlite3.Connection.create_function
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:499: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:513: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:516: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.txt:516: WARNING: py:mod reference target not found: os.path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.1.7.txt:12: WARNING: py:func reference target not found: urllib.parse.parse_qsl
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:238: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:241: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:377: WARNING: py:mod reference target not found: pathlib
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:377: WARNING: py:class reference target not found: os.PathLike
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.time
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: decimal.Decimal
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:406: WARNING: py:class reference target not found: uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:520: WARNING: py:func reference target not found: copy.deepcopy
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:525: WARNING: py:mod reference target not found: faulthandler
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:667: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:702: WARNING: py:func reference target not found: urllib.parse.parse_qsl
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:705: WARNING: py:meth reference target not found: unittest.TestCase.addCleanup
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:705: WARNING: py:meth reference target not found: unittest.TestCase.setUp
/builddir/build/BUILD/Django-4.2.3/docs/releases/3.2.txt:760: WARNING: py:func reference target not found: copy.deepcopy
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:34: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:37: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:42: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:292: WARNING: py:data reference target not found: sys.__interactivehook__
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:349: WARNING: py:data reference target not found: sys.stdout
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:349: WARNING: py:func reference target not found: print
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:373: WARNING: undefined label: 'logger'
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.0.txt:590: WARNING: py:attr reference target not found: datetime.timezone.utc
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.1.txt:369: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.1.txt:404: WARNING: py:mod reference target not found: multiprocessing
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.1.txt:538: WARNING: py:func reference target not found: unittest.expectedFailure
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.1.txt:699: WARNING: py:attr reference target not found: datetime.timezone.utc
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.1.txt:699: WARNING: py:attr reference target not found: datetime.timezone.utc
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.2.txt:164: WARNING: py:class reference target not found: pathlib.Path
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.2.txt:466: WARNING: py:attr reference target not found: ssl.SSLContext.check_hostname
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.2.txt:466: WARNING: py:attr reference target not found: ssl.SSLContext.verify_mode
/builddir/build/BUILD/Django-4.2.3/docs/releases/4.2.txt:554: WARNING: py:mod reference target not found: secrets
/builddir/build/BUILD/Django-4.2.3/docs/topics/async.txt:252: WARNING: py:func reference target not found: asyncio.run
/builddir/build/BUILD/Django-4.2.3/docs/topics/auth/passwords.txt:609: WARNING: py:meth reference target not found: difflib.SequenceMatcher.quick_ratio
/builddir/build/BUILD/Django-4.2.3/docs/topics/cache.txt:370: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/models.txt:160: WARNING: term not in glossary: 'sequence'
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/queries.txt:441: WARNING: undefined label: 'tut-keywordargs'
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/queries.txt:731: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/queries.txt:1668: WARNING: unknown document: 'python:howto/descriptor'
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/sql.txt:336: WARNING: py:func reference target not found: collections.namedtuple
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/transactions.txt:116: WARNING: term not in glossary: 'decorator'
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/transactions.txt:126: WARNING: term not in glossary: 'context manager'
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/transactions.txt:316: WARNING: py:func reference target not found: functools.partial
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/transactions.txt:397: WARNING: undefined label: 'psycopg:two-phase-commit'
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/transactions.txt:626: WARNING: py:mod reference target not found: sqlite3
/builddir/build/BUILD/Django-4.2.3/docs/topics/db/transactions.txt:629: WARNING: py:mod reference target not found: sqlite3
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:8: WARNING: py:mod reference target not found: smtplib
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:59: WARNING: py:exc reference target not found: smtplib.SMTPException
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:59: WARNING: py:mod reference target not found: smtplib
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:59: WARNING: py:exc reference target not found: smtplib.SMTPException
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:284: WARNING: py:class reference target not found: email.mime.base.MIMEBase
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:323: WARNING: py:class reference target not found: email.mime.text.MIMEText
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:340: WARNING: py:class reference target not found: email.mime.base.MIMEBase
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:356: WARNING: py:class reference target not found: email.message.Message
/builddir/build/BUILD/Django-4.2.3/docs/topics/email.txt:511: WARNING: py:func reference target not found: socket.getdefaulttimeout
/builddir/build/BUILD/Django-4.2.3/docs/topics/http/sessions.txt:283: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/topics/http/sessions.txt:285: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/topics/http/sessions.txt:340: WARNING: py:mod reference target not found: pickle
/builddir/build/BUILD/Django-4.2.3/docs/topics/http/sessions.txt:698: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/topics/http/urls.txt:43: WARNING: term not in glossary: 'sequence'
/builddir/build/BUILD/Django-4.2.3/docs/topics/http/urls.txt:128: WARNING: py:class reference target not found: uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/topics/http/urls.txt:331: WARNING: term not in glossary: 'sequence'
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:34: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:55: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:55: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:82: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:90: WARNING: py:class reference target not found: datetime.time
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:109: WARNING: py:mod reference target not found: zoneinfo
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:115: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:143: WARNING: py:meth reference target not found: datetime.datetime.fromtimestamp
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:143: WARNING: py:attr reference target not found: datetime.timezone.utc
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:160: WARNING: py:func reference target not found: zoneinfo.available_timezones
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:372: WARNING: py:class reference target not found: datetime.tzinfo
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:576: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:598: WARNING: py:meth reference target not found: datetime.datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:598: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:598: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:635: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:635: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/timezones.txt:709: WARNING: py:func reference target not found: zoneinfo.available_timezones
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/translation.txt:131: WARNING: undefined label: 'f-strings'
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/translation.txt:491: WARNING: py:meth reference target not found: str.format
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/translation.txt:491: WARNING: py:meth reference target not found: str.format
/builddir/build/BUILD/Django-4.2.3/docs/topics/i18n/translation.txt:1747: WARNING: undefined label: 'old-string-formatting'
/builddir/build/BUILD/Django-4.2.3/docs/topics/install.txt:142: WARNING: unknown document: 'python:tutorial/venv'
/builddir/build/BUILD/Django-4.2.3/docs/topics/logging.txt:21: WARNING: py:mod reference target not found: logging
/builddir/build/BUILD/Django-4.2.3/docs/topics/logging.txt:123: WARNING: undefined label: 'python:logrecord-attributes'
/builddir/build/BUILD/Django-4.2.3/docs/topics/logging.txt:169: WARNING: undefined label: 'logging-config-dictschema'
/builddir/build/BUILD/Django-4.2.3/docs/topics/logging.txt:202: WARNING: undefined label: 'logging-config-dictschema'
/builddir/build/BUILD/Django-4.2.3/docs/topics/logging.txt:367: WARNING: undefined label: 'formatter-objects'
/builddir/build/BUILD/Django-4.2.3/docs/topics/logging.txt:389: WARNING: py:class reference target not found: logging.StreamHandler
/builddir/build/BUILD/Django-4.2.3/docs/topics/logging.txt:420: WARNING: py:func reference target not found: logging.config.dictConfig
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:778: WARNING: py:func reference target not found: functools.partial
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:778: WARNING: py:class reference target not found: functools.partialmethod
generating indices... /builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:780: WARNING: py:mod reference target not found: pathlib
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:780: WARNING: py:class reference target not found: pathlib.PosixPath
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:780: WARNING: py:class reference target not found: pathlib.PurePosixPath
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:783: WARNING: py:class reference target not found: os.PathLike
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:783: WARNING: py:class reference target not found: os.DirEntry
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:783: WARNING: py:func reference target not found: os.fspath
/builddir/build/BUILD/Django-4.2.3/docs/topics/migrations.txt:808: WARNING: py:class reference target not found: decimal.Decimal
/builddir/build/BUILD/Django-4.2.3/docs/topics/performance.txt:210: WARNING: term not in glossary: 'generator'
/builddir/build/BUILD/Django-4.2.3/docs/topics/performance.txt:210: WARNING: term not in glossary: 'generator expression'
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:266: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:266: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:295: WARNING: py:class reference target not found: json.JSONEncoder
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:300: WARNING: py:class reference target not found: datetime.datetime
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:303: WARNING: py:class reference target not found: datetime.date
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:306: WARNING: py:class reference target not found: datetime.time
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:311: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:314: WARNING: py:class reference target not found: decimal.Decimal
/builddir/build/BUILD/Django-4.2.3/docs/topics/serialization.txt:314: WARNING: py:class reference target not found: uuid.UUID
/builddir/build/BUILD/Django-4.2.3/docs/topics/signing.txt:119: WARNING: py:mod reference target not found: hashlib
/builddir/build/BUILD/Django-4.2.3/docs/topics/signing.txt:205: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/topics/signing.txt:216: WARNING: py:class reference target not found: datetime.timedelta
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/advanced.txt:489: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/advanced.txt:597: WARNING: py:mod reference target not found: faulthandler
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/advanced.txt:611: WARNING: undefined label: 'logger'
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/advanced.txt:672: WARNING: py:meth reference target not found: argparse.ArgumentParser.add_argument
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/index.txt:23: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:20: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:23: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:43: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:48: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:63: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:67: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:85: WARNING: undefined label: 'unittest-test-discovery'
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:231: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/overview.txt:339: WARNING: py:mod reference target not found: unittest
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:87: WARNING: py:mod reference target not found: urllib
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:266: WARNING: py:func reference target not found: json.dumps
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:305: WARNING: py:class reference target not found: io.StringIO
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:305: WARNING: py:class reference target not found: io.BytesIO
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:575: WARNING: py:func reference target not found: sys.exc_info
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:587: WARNING: py:func reference target not found: json.loads
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:655: WARNING: py:meth reference target not found: unittest.TestCase.assertRaises
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:688: WARNING: py:class reference target not found: http.cookies.SimpleCookie
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:688: WARNING: py:mod reference target not found: http.cookies
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:787: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:799: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:810: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:867: WARNING: py:exc reference target not found: unittest.SkipTest
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:976: WARNING: py:func reference target not found: copy.deepcopy
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:1601: WARNING: py:class reference target not found: unittest.TestCase
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:1601: WARNING: py:meth reference target not found: unittest.TestCase.assertTrue
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:1601: WARNING: py:meth reference target not found: unittest.TestCase.assertEqual
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:1616: WARNING: py:meth reference target not found: unittest.TestCase.assertRaisesRegex
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:1632: WARNING: py:meth reference target not found: unittest.TestCase.assertWarnsRegex
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:1632: WARNING: py:meth reference target not found: unittest.TestCase.assertRaisesRegex
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:1885: WARNING: py:mod reference target not found: json
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:2167: WARNING: py:func reference target not found: unittest.skipIf
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:2167: WARNING: py:func reference target not found: unittest.skipUnless
/builddir/build/BUILD/Django-4.2.3/docs/topics/testing/tools.txt:2172: WARNING: py:func reference target not found: unittest.skipIf
genindex py-modindex done
highlighting module code... [ 0%] asgiref.sync
highlighting module code... [ 1%] django
highlighting module code... [ 2%] django.apps.config
highlighting module code... [ 2%] django.conf.urls.i18n
highlighting module code... [ 3%] django.contrib.admin
highlighting module code... [ 4%] django.contrib.admin.decorators
highlighting module code... [ 4%] django.contrib.admin.options
highlighting module code... [ 5%] django.contrib.admin.sites
highlighting module code... [ 6%] django.contrib.admin.views.decorators
highlighting module code... [ 7%] django.contrib.auth
highlighting module code... [ 7%] django.contrib.auth.context_processors
highlighting module code... [ 8%] django.contrib.auth.decorators
highlighting module code... [ 9%] django.contrib.auth.hashers
highlighting module code... [ 9%] django.contrib.auth.password_validation
highlighting module code... [ 10%] django.contrib.flatpages.sitemaps
highlighting module code... [ 11%] django.contrib.gis.feeds
highlighting module code... [ 11%] django.contrib.gis.measure
highlighting module code... [ 12%] django.contrib.messages.api
highlighting module code... [ 13%] django.contrib.messages.middleware
highlighting module code... [ 14%] django.contrib.postgres.aggregates.general
highlighting module code... [ 14%] django.contrib.postgres.aggregates.statistics
highlighting module code... [ 15%] django.contrib.postgres.constraints
highlighting module code... [ 16%] django.contrib.postgres.expressions
highlighting module code... [ 16%] django.contrib.postgres.fields.array
highlighting module code... [ 17%] django.contrib.postgres.fields.citext
highlighting module code... [ 18%] django.contrib.postgres.fields.hstore
highlighting module code... [ 19%] django.contrib.postgres.fields.ranges
highlighting module code... [ 19%] django.contrib.postgres.forms.array
highlighting module code... [ 20%] django.contrib.postgres.forms.hstore
highlighting module code... [ 21%] django.contrib.postgres.forms.ranges
highlighting module code... [ 21%] django.contrib.postgres.functions
highlighting module code... [ 22%] django.contrib.postgres.indexes
highlighting module code... [ 23%] django.contrib.postgres.operations
highlighting module code... [ 23%] django.contrib.postgres.search
highlighting module code... [ 24%] django.contrib.postgres.validators
highlighting module code... [ 25%] django.contrib.sessions.exceptions
highlighting module code... [ 26%] django.contrib.sessions.middleware
highlighting module code... [ 26%] django.contrib.sitemaps
highlighting module code... [ 27%] django.contrib.sites.middleware
highlighting module code... [ 28%] django.core.checks.messages
highlighting module code... [ 28%] django.core.exceptions
highlighting module code... [ 29%] django.core.files.base
highlighting module code... [ 30%] django.core.files.images
highlighting module code... [ 30%] django.core.files.storage
highlighting module code... [ 31%] django.core.files.storage.base
highlighting module code... [ 32%] django.core.files.storage.filesystem
highlighting module code... [ 33%] django.core.files.storage.memory
highlighting module code... [ 33%] django.core.files.uploadedfile
highlighting module code... [ 34%] django.core.files.uploadhandler
highlighting module code... [ 35%] django.core.mail
highlighting module code... [ 35%] django.core.mail.message
highlighting module code... [ 36%] django.core.management.base
highlighting module code... [ 37%] django.core.paginator
highlighting module code... [ 38%] django.core.signing
highlighting module code... [ 38%] django.core.validators
highlighting module code... [ 39%] django.db.backends.base.schema
highlighting module code... [ 40%] django.db.migrations.operations.fields
highlighting module code... [ 40%] django.db.migrations.operations.models
highlighting module code... [ 41%] django.db.migrations.operations.special
highlighting module code... [ 42%] django.db.models.aggregates
highlighting module code... [ 42%] django.db.models.base
highlighting module code... [ 43%] django.db.models.constraints
highlighting module code... [ 44%] django.db.models.deletion
highlighting module code... [ 45%] django.db.models.expressions
highlighting module code... [ 45%] django.db.models.fields
highlighting module code... [ 46%] django.db.models.fields.files
highlighting module code... [ 47%] django.db.models.fields.json
highlighting module code... [ 47%] django.db.models.fields.related
highlighting module code... [ 48%] django.db.models.functions.comparison
highlighting module code... [ 49%] django.db.models.functions.datetime
highlighting module code... [ 50%] django.db.models.functions.math
highlighting module code... [ 50%] django.db.models.functions.text
highlighting module code... [ 51%] django.db.models.functions.window
highlighting module code... [ 52%] django.db.models.indexes
highlighting module code... [ 52%] django.db.models.lookups
highlighting module code... [ 53%] django.db.models.manager
highlighting module code... [ 54%] django.db.models.options
highlighting module code... [ 54%] django.db.models.query
highlighting module code... [ 55%] django.db.models.query_utils
highlighting module code... [ 56%] django.db.transaction
highlighting module code... [ 57%] django.db.utils
highlighting module code... [ 57%] django.dispatch.dispatcher
highlighting module code... [ 58%] django.forms.boundfield
highlighting module code... [ 59%] django.forms.fields
highlighting module code... [ 59%] django.forms.forms
highlighting module code... [ 60%] django.forms.formsets
highlighting module code... [ 61%] django.forms.models
highlighting module code... [ 61%] django.forms.renderers
highlighting module code... [ 62%] django.forms.widgets
highlighting module code... [ 63%] django.http.request
highlighting module code... [ 64%] django.http.response
highlighting module code... [ 64%] django.middleware.cache
highlighting module code... [ 65%] django.middleware.clickjacking
highlighting module code... [ 66%] django.middleware.common
highlighting module code... [ 66%] django.middleware.csrf
highlighting module code... [ 67%] django.middleware.gzip
highlighting module code... [ 68%] django.middleware.http
highlighting module code... [ 69%] django.middleware.locale
highlighting module code... [ 69%] django.middleware.security
highlighting module code... [ 70%] django.shortcuts
highlighting module code... [ 71%] django.template.backends.django
highlighting module code... [ 71%] django.template.backends.jinja2
highlighting module code... [ 72%] django.template.base
highlighting module code... [ 73%] django.template.context
highlighting module code... [ 73%] django.template.context_processors
highlighting module code... [ 74%] django.template.engine
highlighting module code... [ 75%] django.template.exceptions
highlighting module code... [ 76%] django.template.loader
highlighting module code... [ 76%] django.template.loaders.base
highlighting module code... [ 77%] django.template.response
highlighting module code... [ 78%] django.test.client
highlighting module code... [ 78%] django.test.runner
highlighting module code... [ 79%] django.test.testcases
highlighting module code... [ 80%] django.test.utils
highlighting module code... [ 80%] django.urls.base
highlighting module code... [ 81%] django.urls.conf
highlighting module code... [ 82%] django.urls.converters
highlighting module code... [ 83%] django.urls.exceptions
highlighting module code... [ 83%] django.urls.resolvers
highlighting module code... [ 84%] django.utils.cache
highlighting module code... [ 85%] django.utils.dateparse
highlighting module code... [ 85%] django.utils.decorators
highlighting module code... [ 86%] django.utils.encoding
highlighting module code... [ 87%] django.utils.feedgenerator
highlighting module code... [ 88%] django.utils.functional
highlighting module code... [ 88%] django.utils.html
highlighting module code... [ 89%] django.utils.http
highlighting module code... [ 90%] django.utils.log
highlighting module code... [ 90%] django.utils.module_loading
highlighting module code... [ 91%] django.utils.safestring
highlighting module code... [ 92%] django.utils.text
highlighting module code... [ 92%] django.utils.timezone
highlighting module code... [ 93%] django.utils.translation
highlighting module code... [ 94%] django.views.debug
highlighting module code... [ 95%] django.views.decorators.cache
highlighting module code... [ 95%] django.views.decorators.common
highlighting module code... [ 96%] django.views.decorators.csrf
highlighting module code... [ 97%] django.views.decorators.debug
highlighting module code... [ 97%] django.views.decorators.http
highlighting module code... [ 98%] django.views.decorators.vary
highlighting module code... [ 99%] django.views.generic.dates
highlighting module code... [100%] django.views.i18n
writing additional pages... search done
copying images... [ 4%] howto/_images/postmortem.png
copying images... [ 8%] howto/_images/template-lines.png
copying images... [ 12%] internals/_images/triage_process.svg
copying images... [ 16%] intro/_images/admin01.png
copying images... [ 20%] intro/_images/admin02.png
copying images... [ 25%] intro/_images/admin03t.png
copying images... [ 29%] intro/_images/admin04t.png
copying images... [ 33%] intro/_images/admin05t.png
copying images... [ 37%] intro/_images/admin06t.png
copying images... [ 41%] intro/_images/admin07.png
copying images... [ 45%] intro/_images/admin08t.png
copying images... [ 50%] intro/_images/admin09.png
copying images... [ 54%] intro/_images/admin10t.png
copying images... [ 58%] intro/_images/admin14t.png
copying images... [ 62%] intro/_images/admin11t.png
copying images... [ 66%] intro/_images/admin12t.png
copying images... [ 70%] intro/_images/admin13t.png
copying images... [ 75%] ref/contrib/admin/_images/admin-actions.png
copying images... [ 79%] ref/contrib/admin/_images/adding-actions-to-the-modeladmin.png
copying images... [ 83%] ref/contrib/admin/_images/actions-as-modeladmin-methods.png
copying images... [ 87%] ref/contrib/admin/_images/list_filter.png
copying images... [ 91%] ref/contrib/admin/_images/fieldsets.png
copying images... [ 95%] ref/contrib/admin/_images/raw_id_fields.png
copying images... [100%] topics/testing/_images/django_unittest_classes_hierarchy.svg
copying static files... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
writing templatebuiltins.js...
build succeeded, 530 warnings.
The HTML pages are in _build/html.
Build finished. The HTML pages are in _build/html.
+ cp -ar docs ..
+ mkdir -p /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/man/man1/
+ cp -p docs/man/django-admin.1 /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/man/man1/
++ pkg-config --variable=completionsdir bash-completion
+ bashcompdir=/usr/share/bash-completion/completions
+ mkdir -p /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/bash-completion/completions
+ install -m 0644 -p extras/django_bash_completion /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/bash-completion/completions/django-admin.py
+ for file in django-admin django-admin-3 django-admin-3.12 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/bash-completion/completions/django-admin
+ for file in django-admin django-admin-3 django-admin-3.12 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/bash-completion/completions/django-admin-3
+ for file in django-admin django-admin-3 django-admin-3.12 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/bash-completion/completions/django-admin-3.12
+ for file in django-admin django-admin-3 django-admin-3.12 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/bash-completion/completions/python3-django-admin
+ for file in django-admin django-admin-3 django-admin-3.12 python3-django-admin manage.py
+ ln -s django-admin.py /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/bash-completion/completions/manage.py
+ ln -s ./django-admin /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin/django-admin-3
+ ln -s ./django-admin /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin/django-admin-3.12
+ ln -s ./django-admin /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/bin/python3-django-admin
+ find /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64 -name '*.po'
+ xargs rm -f
+ sed -i '/.po$/d' /builddir/build/BUILD/python-django-4.2.3-1.fc40.x86_64-pyproject-files
+ /usr/bin/find-debuginfo -j2 --strict-build-id -m -i --build-id-seed 4.2.3-1.fc40 --unique-debug-suffix -4.2.3-1.fc40.x86_64 --unique-debug-src-base python-django-4.2.3-1.fc40.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/Django-4.2.3
find-debuginfo: starting
Extracting debug info from 0 files
Creating .debug symlinks for symlinks to ELF files
find: 'debug': No such file or directory
find-debuginfo: done
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/check-rpaths
+ /usr/lib/rpm/redhat/brp-mangle-shebangs
+ /usr/lib/rpm/brp-remove-la-files
+ env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j2
Bytecompiling .py files below /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/lib/python3.12 using python3.12
+ /usr/lib/rpm/redhat/brp-python-hardlink
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.nd42xi
+ umask 022
+ cd /builddir/build/BUILD
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules '
+ export FCFLAGS
+ VALAFLAGS=-g
+ export VALAFLAGS
+ RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn'
+ export RUSTFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes '
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ cd Django-4.2.3
+ cd /builddir/build/BUILD/Django-4.2.3
++ pwd
+ export PYTHONPATH=/builddir/build/BUILD/Django-4.2.3
+ PYTHONPATH=/builddir/build/BUILD/Django-4.2.3
+ cd tests
+ /usr/bin/python3 runtests.py --settings=test_sqlite --verbosity=2 --parallel 1 -k 'not test_safe_mime_multipart and not test_unicode_address_header'
Testing against Django installed in '/builddir/build/BUILD/Django-4.2.3/django'
Importing application xor_lookups
Importing application wsgi
Importing application view_tests
Importing application version
Importing application validators
Importing application validation
Importing application utils_tests
Importing application user_commands
Importing application urlpatterns_reverse
Importing application urlpatterns
Importing application update_only_fields
Importing application update
Importing application unmanaged_models
Importing application transactions
Importing application transaction_hooks
Importing application timezones
Importing application test_utils
Importing application test_runner
Importing application test_exceptions
Importing application test_client_regress
Importing application test_client
Importing application template_tests
Importing application template_loader
Importing application template_backends
Importing application syndication_tests
Importing application swappable_models
Importing application string_lookup
Importing application str
Importing application staticfiles_tests
Importing application sites_tests
Importing application sites_framework
Importing application sitemaps_tests
Importing application signing
Importing application signed_cookies_tests
Importing application signals
Importing application shortcuts
Importing application shell
Importing application settings_tests
Importing application sessions_tests
Importing application servers
Importing application serializers
Importing application select_related_regress
Importing application select_related_onetoone
Importing application select_related
Importing application select_for_update
Importing application schema
Importing application save_delete_hooks
Importing application reverse_lookup
Importing application responses
Importing application resolve_url
Importing application reserved_names
Importing application requests_tests
Importing application django.contrib.redirects
Importing application redirects_tests
Importing application raw_query
Importing application queryset_pickle
Importing application queries
Importing application proxy_models
Importing application proxy_model_inheritance
Importing application properties
Importing application project_template
Importing application prefetch_related
Importing application postgres_tests
Importing application pagination
Importing application ordering
Importing application order_with_respect_to
Importing application or_lookups
Importing application one_to_one
Importing application null_queries
Importing application null_fk_ordering
Importing application null_fk
Importing application no_models
Importing application nested_foreign_keys
Importing application mutually_referential
Importing application multiple_database
Importing application modeladmin
Importing application model_utils
Importing application model_regress
Importing application model_package
Importing application model_options
Importing application model_meta
Importing application model_inheritance_regress
Importing application model_inheritance
Importing application model_indexes
Importing application model_formsets_regress
Importing application model_formsets
Importing application model_forms
Importing application model_fields
Importing application model_enums
Importing application migrations2
Importing application migrations
Importing application migration_test_data_persistence
Importing application migrate_signals
Importing application middleware_exceptions
Importing application middleware
Importing application messages_tests
Importing application max_lengths
Importing application many_to_one_null
Importing application many_to_one
Importing application many_to_many
Importing application managers_regress
Importing application mail
Importing application m2o_recursive
Importing application m2m_through_regress
Importing application m2m_through
Importing application m2m_signals
Importing application m2m_regress
Importing application m2m_recursive
Importing application m2m_multiple
Importing application m2m_intermediary
Importing application m2m_and_m2o
Importing application lookup
Importing application logging_tests
Importing application known_related_objects
Importing application invalid_models_tests
Importing application introspection
Importing application inspectdb
Importing application inline_formsets
Importing application indexes
Importing application i18n
Importing application humanize_tests
Importing application httpwrappers
Importing application handlers
Importing application get_or_create
Importing application get_object_or_404
Importing application get_earliest_or_latest
Importing application generic_views
Importing application generic_relations_regress
Importing application generic_relations
Importing application generic_inline_admin
Importing application from_db_value
Importing application forms_tests
Importing application foreign_object
Importing application force_insert_update
Importing application django.contrib.flatpages
Importing application flatpages_tests
Importing application fixtures_regress
Importing application fixtures_model_package
Importing application fixtures
Importing application filtered_relation
Importing application files
Importing application file_uploads
Importing application file_storage
Importing application field_subclassing
Importing application field_defaults
Importing application field_deconstruction
Importing application extra_regress
Importing application expressions_window
Importing application expressions_case
Importing application expressions
Importing application empty_models
Importing application empty
Importing application distinct_on_fields
Importing application dispatch
Importing application deprecation
Importing application delete_regress
Importing application delete
Importing application defer_regress
Importing application defer
Importing application decorators
Importing application dbshell
Importing application db_utils
Importing application db_typecasts
Importing application db_functions
Importing application datetimes
Importing application dates
Importing application datatypes
Importing application custom_pk
Importing application custom_migration_operations
Importing application custom_methods
Importing application custom_managers
Importing application custom_lookups
Importing application custom_columns
Importing application csrf_tests
Importing application context_processors
Importing application contenttypes_tests
Importing application constraints
Importing application conditional_processing
Importing application check_framework
Importing application cache
Importing application bulk_create
Importing application builtin_server
Importing application basic
Importing application bash_completion
Importing application base
Importing application backends
Importing application auth_tests
Importing application async
Importing application asgi
Importing application apps
Importing application app_loading
Importing application annotations
Importing application aggregation_regress
Importing application aggregation
Importing application admin_widgets
Importing application admin_views
Importing application admin_utils
Importing application admin_scripts
Importing application admin_registration
Importing application admin_ordering
Importing application admin_inlines
Importing application admin_filters
Importing application admin_docs
Importing application admin_default_site
Importing application admin_custom_urls
Importing application admin_checks
Importing application admin_changelist
Importing application admin_autodiscover
Importing application absolute_url_overrides
Found 0 test(s).
Skipping setup of unused database(s): default, other.
System check identified no issues (21 silenced).
----------------------------------------------------------------------
Ran 0 tests in 0.000s
NO TESTS RAN
+ RPM_EC=0
++ jobs -p
+ exit 0
Processing files: python-django-bash-completion-4.2.3-1.fc40.noarch
Provides: python-django-bash-completion = 4.2.3-1.fc40
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Processing files: python3-django-doc-4.2.3-1.fc40.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.Hyspkr
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ DOCDIR=/builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ export LC_ALL=C
+ LC_ALL=C
+ export DOCDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/_images /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/_modules /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/_sources /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/_static /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/contents.html /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/faq /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/genindex.html /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/glossary.html /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/howto /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/index.html /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/internals /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/intro /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/misc /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/objects.inv /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/py-modindex.html /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/ref /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/releases /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/search.html /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/searchindex.js /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/templatebuiltins.js /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ cp -pr /builddir/build/BUILD/Django-4.2.3/docs/_build/html/topics /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django-doc
+ RPM_EC=0
++ jobs -p
+ exit 0
Provides: python3-django-doc = 4.2.3-1.fc40
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Suggests: python3-django = 4.2.3-1.fc40
Processing files: python3-django-4.2.3-1.fc40.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.CF1rws
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ DOCDIR=/builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django
+ export LC_ALL=C
+ LC_ALL=C
+ export DOCDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django
+ cp -pr /builddir/build/BUILD/Django-4.2.3/AUTHORS /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django
+ cp -pr /builddir/build/BUILD/Django-4.2.3/README.rst /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/doc/python3-django
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.vRsdoT
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ LICENSEDIR=/builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/licenses/python3-django
+ export LC_ALL=C
+ LC_ALL=C
+ export LICENSEDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/licenses/python3-django
+ cp -pr /builddir/build/BUILD/Django-4.2.3/LICENSE /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64/usr/share/licenses/python3-django
+ RPM_EC=0
++ jobs -p
+ exit 0
Provides: bundled(jquery) = 2.2.3 bundled(xregexp) = 2.0.0 python-django = 4.2.3-1.fc40 python3-django = 4.2.3-1.fc40 python3.12-django = 4.2.3-1.fc40 python3.12dist(django) = 4.2.3 python3dist(django) = 4.2.3
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: (python3.12dist(asgiref) < 4~~ with python3.12dist(asgiref) >= 3.6) /usr/bin/python3 python(abi) = 3.12 python3.12dist(sqlparse) >= 0.3.1
Recommends: (python-django-bash-completion = 4.2.3-1.fc40 if bash)
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64
Wrote: /builddir/build/SRPMS/python-django-4.2.3-1.fc40.src.rpm
Wrote: /builddir/build/RPMS/python3-django-4.2.3-1.fc40.noarch.rpm
Wrote: /builddir/build/RPMS/python-django-bash-completion-4.2.3-1.fc40.noarch.rpm
Wrote: /builddir/build/RPMS/python3-django-doc-4.2.3-1.fc40.noarch.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.us8w0N
+ umask 022
+ cd /builddir/build/BUILD
+ cd Django-4.2.3
+ /usr/bin/rm -rf /builddir/build/BUILDROOT/python-django-4.2.3-1.fc40.x86_64
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.Na2YJS
+ umask 022
+ cd /builddir/build/BUILD
+ rm -rf /builddir/build/BUILD/Django-4.2.3-SPECPARTS
+ rm -rf Django-4.2.3 Django-4.2.3.gemspec
+ RPM_EC=0
++ jobs -p
+ exit 0
Finish: rpmbuild python-django-4.2.3-1.fc40.src.rpm
Finish: build phase for python-django-4.2.3-1.fc40.src.rpm
INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root/var/log/dnf.rpm.log
/var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root/var/log/dnf.librepo.log
/var/lib/mock/fedora-rawhide-x86_64-1692096785.491105/root/var/log/dnf.log
INFO: Done(/var/lib/copr-rpmbuild/results/python-django-4.2.3-1.fc40.src.rpm) Config(child) 3 minutes 3 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_success=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
Finish: run
Running RPMResults tool